Nutzermeldungen
0
Im Normalbereich. 0 in der letzten Stunde. Üblich sind etwa 0 pro Stunde.
Damn, is it down?
Alle Dienste / Cloud & Entwickler
cloudsigma.com · Cloud & Entwickler
Die Prüfungen sind erfolgreich, die Nutzermeldungen liegen im Normalbereich und die Statusseite des Anbieters meldet keine Probleme.
Live-Diagnose
Findet die wahrscheinlichste Ebene (der Dienst, dein Anbieter oder Gebiet, DNS oder dein WLAN) und gibt zwei Schritte zum Ausprobieren.
Klicke auf „Test starten“Dein Browser testet die Website, uns und zwei öffentliche DNS-Resolver. Wir speichern niemals deine IP, nur anonyme Zählungen nach Netzwerk und Region.
Keine Meldungen in den letzten 24 Stunden.
Punkte stehen für ganze Bundesländer, Provinzen oder Länder, nie für genaue Standorte. Wir speichern keine IP-Adressen. Jede Meldung mit bekanntem Ort kann auf der Karte erscheinen. Aktualisierung jede Minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Im Normalbereich. 0 in der letzten Stunde. Üblich sind etwa 0 pro Stunde.
Erreichbar
Last checked 5 min ago. Last stored result reached it in 210 ms.
Alles in Ordnung
All Systems Operational Offizielle Statusseite
| Zeit (UTC) | Meldungen | Normalwert | Antwortzeit | Fehlgeschlagene Prüfungen |
|---|---|---|---|---|
| 17:30 | 0 | 0.0 | 674 ms | 0 |
| 17:45 | 0 | 0.0 | 279 ms | 0 |
| 18:00 | 0 | 0.0 | 263 ms | 0 |
| 18:15 | 0 | 0.0 | 392 ms | 0 |
| 18:30 | 0 | 0.0 | 308 ms | 0 |
| 18:45 | 0 | 0.0 | 385 ms | 0 |
| 19:00 | 0 | 0.0 | 302 ms | 0 |
| 19:15 | 0 | 0.0 | 279 ms | 0 |
| 19:30 | 0 | 0.0 | 147 ms | 0 |
| 19:45 | 0 | 0.0 | 186 ms | 0 |
| 20:00 | 0 | 0.0 | 269 ms | 0 |
| 20:15 | 0 | 0.0 | 270 ms | 0 |
| 20:30 | 0 | 0.0 | 248 ms | 0 |
| 20:45 | 0 | 0.0 | 259 ms | 0 |
| 21:00 | 0 | 0.0 | 419 ms | 0 |
| 21:15 | 0 | 0.0 | 331 ms | 0 |
| 21:30 | 0 | 0.0 | 255 ms | 0 |
| 21:45 | 0 | 0.0 | 275 ms | 0 |
| 22:00 | 0 | 0.0 | 355 ms | 0 |
| 22:15 | 0 | 0.0 | 418 ms | 0 |
| 22:30 | 0 | 0.0 | 235 ms | 0 |
| 22:45 | 0 | 0.0 | 481 ms | 0 |
| 23:00 | 0 | 0.0 | 291 ms | 0 |
| 23:15 | 0 | 0.0 | 256 ms | 0 |
| 23:30 | 0 | 0.0 | 272 ms | 0 |
| 23:45 | 0 | 0.0 | 295 ms | 0 |
| 00:00 | 0 | 0.0 | 323 ms | 0 |
| 00:15 | 0 | 0.0 | 273 ms | 0 |
| 00:30 | 0 | 0.0 | 313 ms | 0 |
| 00:45 | 0 | 0.0 | 341 ms | 0 |
| 01:00 | 0 | 0.0 | 326 ms | 0 |
| 01:15 | 0 | 0.0 | 302 ms | 0 |
| 01:30 | 0 | 0.0 | 206 ms | 0 |
| 01:45 | 0 | 0.0 | 278 ms | 0 |
| 02:00 | 0 | 0.0 | 458 ms | 0 |
| 02:15 | 0 | 0.0 | 295 ms | 0 |
| 02:30 | 0 | 0.0 | 320 ms | 0 |
| 02:45 | 0 | 0.0 | 456 ms | 0 |
| 03:00 | 0 | 0.0 | 303 ms | 0 |
| 03:15 | 0 | 0.0 | 291 ms | 0 |
| 03:30 | 0 | 0.0 | 231 ms | 0 |
| 03:45 | 0 | 0.0 | 225 ms | 0 |
| 04:00 | 0 | 0.0 | 334 ms | 0 |
| 04:15 | 0 | 0.0 | 312 ms | 0 |
| 04:30 | 0 | 0.0 | 436 ms | 0 |
| 04:45 | 0 | 0.0 | 261 ms | 0 |
| 05:00 | 0 | 0.0 | 259 ms | 0 |
| 05:15 | 0 | 0.0 | 194 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 12 days of data so far, so the 90-day numbers fill in over time.
[TYO] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Tokyo cloud location. The maintenance is required to address a critical security vulnerability and ensure the continued security and reliability of our services. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility…
[CRK] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Clark cloud location. The maintenance is required to address a critical security vulnerability and ensure the continued security and reliability of our services. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility…
[DUS] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Düsseldorf cloud location. The maintenance is required to address a critical security vulnerability and ensure the continued security and reliability of our services. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network…
[DUB] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Dublin cloud location. The maintenance is required to address a critical security vulnerability and ensure the continued security and reliability of our services. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility…
[GVA] API Server Maintenance
CloudSigma would like to inform you of scheduled maintenance on the API server in our Geneva/Zurich cloud location. The purpose of this maintenance is to complete the decommissioning of the former API endpoint, zrh.cloudsigma.com, following the migration to gva.cloudsigma.com on 19 September 2026. This maintenance will ensure that all API requests are handled exclusively through the new…
[RUH] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform an emergency maintenance of our API server in the Riyadh cloud location. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility, and/or any other running services. During the maintenance, customers will not be able to perform any calls to the API, directly or through…
[MNL2] Network Maintenance
CloudSigma would like to inform you that we are planning to perform a scheduled maintenance of our Network infrastructure of the Manila 2 cloud. More precisely, we will be performing upgrades on the routers supporting the cloud. IMPACT: There will be no impact on already existing/running customers’ virtual machines, hosts, network accessibility, and/or any other running services.
[MNL2] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Manila 2 cloud location. The maintenance is required to address a critical security vulnerability and ensure the continued security and reliability of our services. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility…
[PER] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Perth cloud location. The maintenance is required to address a critical security vulnerability and ensure the continued security and reliability of our services. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility…
[CAI] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Cairo cloud location. The maintenance is required to address a critical security vulnerability and ensure the continued security and reliability of our services. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility…
[FRA] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Frankfurt cloud location. The maintenance is required to address a critical security vulnerability and ensure the continued security and reliability of our services. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility…
[MNL2] Network Maintenance
CloudSigma would like to inform you that we are planning to perform a scheduled maintenance of our Network infrastructure of the Manila 2 cloud. More precisely, we will be performing upgrades on the routers supporting the cloud. IMPACT: There will be no impact on already existing/running customers’ virtual machines, hosts, network accessibility, and/or any other running services.
[JHB] Emergency API Server Maintenance
CloudSigma would like to inform you that we are planning to perform emergency maintenance of our API server in the Johor cloud location. The maintenance is required to address a critical security vulnerability and ensure the continued security and reliability of our services. IMPACT: There will be no impact on already existing/running customer’s virtual machines, hosts, network accessibility…
[FRA] Storage Cluster Maintenance
CloudSigma would like to inform you that we are planning to do scheduled maintenance of our storage cluster in the Frankfurt cloud location. The maintenance aims to perform OS upgrades of the storage nodes sustaining the cloud's storage cluster. IMPACT: There will be no service impact, except a slight increase in the I/O operations.
[FRA] Storage Cluster Maintenance - Stage 2
CloudSigma would like to inform you that we are planning to do scheduled maintenance of our storage cluster in the Frankfurt cloud location. The maintenance aims to perform OS upgrades of the storage nodes sustaining the cloud's storage cluster. IMPACT: There will be no service impact, except a slight increase in the I/O operations.
[MNL] Network Maintenance
CloudSigma would like to inform you that we are planning to perform a scheduled maintenance of our Network infrastructure of the Manila cloud. More precisely, we will be performing upgrades on the routers supporting the cloud. IMPACT: There will be no impact on already existing/running customers’ virtual machines, hosts, network accessibility, and/or any other running services.
Geplante Wartung ist keine Störung. Zeiten und Wortlaut stammen vom Anbieter. Outage Weather →
Für Cloudsigma sind noch keine Störungen erfasst. Störungen ab 10 Minuten bekommen hier eine eigene Seite.
Eine Meldung pro Dienst alle 10 Minuten aus diesem Netzwerk. Kein Konto nötig.
Erhalte eine E-Mail, wenn Cloudsigma ausfällt und wenn es wieder läuft. Kostenlos. Bestätigung per E-Mail, jederzeit abbestellbar.
Lieber in einem Team-Channel? Benachrichtigungen zu Cloudsigma an Slack, Discord oder einen Webhook senden – kostenlos.
Cloudsigma ist bei uns in der Kategorie Cloud & Entwickler gelistet und wird unter cloudsigma.com geprüft.
Cloudsigma veröffentlicht eine offizielle Statusseite unter status.cloudsigma.com; wenn wir sie lesen können, fließt die dort gemeldete Vorfallsstufe in den hier angezeigten Status ein.
Typische Probleme bei Diensten der Kategorie Cloud & Entwickler: API-Fehler, fehlgeschlagene Deployments oder Builds und Ausfälle von Dashboard oder Konsole.
Gemessene Verfügbarkeit aus unseren Prüfungen: 100% über 12 Tage mit Prüfungen. Keine öffentlichen Vorfälle seit Beginn der Überwachung vor 12 Tagen erfasst.
Antwortzeit in den letzten 24 Stunden: durchschnittlich 309 ms, Spanne 94–696 ms über 180 erfolgreiche Prüfungen.
Die Prüfungen sind erfolgreich, die Nutzermeldungen liegen im Normalbereich und die Statusseite des Anbieters meldet keine Probleme.
Wir haben seit Beginn der Überwachung vor 12 Tagen keinen öffentlichen Vorfall bei Cloudsigma erfasst.
Aus unseren eigenen Prüfungen: 100% über 12 Tage mit Prüfungen.
Durchschnittlich 309 ms in den letzten 24 Stunden (94–696 ms).
Ja, unter https://status.cloudsigma.com.
Meist liegt es an dir vor Ort: Probiere einen anderen Browser oder die App, wechsle zwischen WLAN und mobilen Daten und leere den Cache. Achte bei Diensten der Kategorie Cloud & Entwickler auf API-Fehler, fehlgeschlagene Deployments oder Builds und Ausfälle von Dashboard oder Konsole. Wenn hier viele Leute gleichzeitig Probleme mit Cloudsigma melden, liegt der Fehler bei Cloudsigma.
Wie wir Ausfälle erkennen und prüfen · Diese Meldung anfechten · Wir prüfen Anfechtungen innerhalb von 24 Stunden.
Community comments
Share what you are seeing with Cloudsigma. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.