All systems operational
Refreshed
CuByte Status
This is the official status page of CuByte's global infrastructure. All related incidents will be published here. Contact our network operations center. Alternatively you can create a ticket in the CuByte Support Center.
Components
FRA1 - Telehouse ?
Operational
Network Core ?
Operational
Incidents
Network Peer AS3223 ?
Operational
Incidents
Network Peer AS47447 ?
Operational
Incidents
Power & UPS ?
Operational
Incidents
Cooling ?
Operational
Incidents
Cloud Server
Operational
Compute Nodes FRA1 ?
Operational
Incidents
Storage Nodes FRA1 ?
Operational
Incidents
Dedicated Server
Operational
Dedicated Server FRA1 ?
Operational
Incidents
CuByte Public Services
Operational
Nameserver ?
Operational
Incidents
Mailing Service ?
Operational
Incidents
Authentication Service (SSO) ?
Operational
Incidents
Public Web Gateway ?
Operational
Incidents
Git & Deployment ?
Operational
Incidents
File Cloud ?
Operational
Incidents
CuByte Internal Services
Operational
Kubernetes Orchestrator ?
Operational
Incidents
VoIP Server (PBX) ?
Operational
Incidents
Core Infrastructure status of Telehouse Frankfurt colocation in Kleyerstraße 75-87
Issues with CuByte's redundant n*10G network core
Issues with uplink provider network Voxility
Issues with uplink provider network 23m
Issues with redundant power feeds or battery backup
Issues with cooling system
Issues with compute nodes from private cloud cluster
Issues of ceph storage servers hosting virtual machines of private cloud cluster
Issues with customer dedicated servers
Issues with the DNS cluster
master.cubyte.name
slave1.cubyte.name
slave2.cubyte.name Issues with the distributed CuByte mailing service (MX) Issues with the single sign on service at auth.app.cubyte.cloud Issues with central web proxies and load balancers Issues with the public deployment servers Issues with the public file cloud Issues with the central Kubernetes Orchestration platform Issues with our VoIP infrastructure
master.cubyte.name
slave1.cubyte.name
slave2.cubyte.name Issues with the distributed CuByte mailing service (MX) Issues with the single sign on service at auth.app.cubyte.cloud Issues with central web proxies and load balancers Issues with the public deployment servers Issues with the public file cloud Issues with the central Kubernetes Orchestration platform Issues with our VoIP infrastructure
Incident history
No incidents reported.Maintenance
No maintenance reported.Past maintenance
March
Network: Maintenance of Lumen transit connection
Mar 13, 2023 22:00 - Mar 14, 2023 01:00 | GMT+01:00
Lumen (AS3356) intends to carry out an internal maintenance within its network.
We do not expect any downtime during the process due to the redundant design and connectivity of our network.
The expected duration is 1 hour.
Affected components
- FRA1 - Telehouse: Network Peer AS47447