Last checked
Hosted status pages for transparent incident communication.
Întâmpini o problemă?
Este Statusio nefuncțional?
Status unavailable
Împărtășește experiența ta pentru a-i ține și pe ceilalți la curent.
Status verification pending
The latest official observation is not fresh enough to confirm current service health.
Official provider statusOfficial maintenance active
Upstream AWS CloudFront DNS Resolution Errors & Propagation Delays — February 10, 2026 21:40 UTC Investigating - On February 10, AWS experienced DNS resolution errors (NXDOMAIN responses) affecting a subset of CloudFront distributions globally. During this period, AWS also reported delays in propagating certain configuration changes, including DNS, TLS-related updates, and cache invalidations. While we did not observe broad impact across the status pages we actively monitor, based on AWS reporting and customer feedback, some custom domains may have experienced brief DNS resolution failures during the affected window. Additionally, some cache invalidations may have been delayed, which could have temporarily prevented recent incident or maintenance updates from appearing immediately on certain status pages. This issue originated from an upstream AWS CloudFront service disruption. February 11, 2026 04:18 UTC Resolved - AWS mitigated the DNS resolution errors and fully resolved the CloudFront configuration change propagation and cache invalidation delays by 04:18 UTC on February 11. All related AWS services are operating normally. Status.io infrastructure and monitoring systems continued operating normally throughout the event. Any delayed cache invalidations have since been processed, and status pages should now reflect the correct state.
Official provider statusOfficial maintenance active
Maintenance display issue — February 3, 2026 16:15 UTC Identified - We’ve identified a production change deployed yesterday that could prevent some scheduled maintenance events from appearing on status pages with more than 1,000 total maintenance events. This issue is limited to display behavior only and does not affect maintenance execution or underlying system functionality. We are rolling back the change in production. February 3, 2026 16:50 UTC Monitoring - The rollback has been deployed and we are monitoring to confirm that maintenance events are displaying correctly across all status pages. We’ll post a final update once monitoring is complete and the incident is resolved. February 3, 2026 17:50 UTC Resolved - Monitoring has confirmed that maintenance events are now displaying correctly across all status pages following the rollback. This issue was limited to display behavior only and affected status pages with a large number of maintenance events (over 1,000). No maintenance schedules or underlying system functionality were affected. The incident is now resolved. We are reviewing the change that caused the issue to reduce the risk of similar issues in the future.
Official provider status0 înregistrări individuale în ultimele 24 de ore. Lista include importuri istorice; totalurile agregate ale sursei sunt afișate în grafic.
Observații ale statusului oficial, nu măsurători directe ale disponibilității.
| Numele componentei | Stare |
|---|---|
| Status Statusio Public Status Pages - US-East | Funcțional |
| Status Statusio Public Status Pages - US-West | Funcțional |
| Status Statusio Public Status Pages - Ireland | Funcțional |
| Status Statusio Public Status Pages - Toronto | Funcțional |
| Status Statusio Private Status Pages - US-East | Funcțional |
| Status Statusio Private Status Pages - US-West | Funcțional |
| Status Statusio Private Status Pages - Ireland | Funcțional |
| Status Statusio Private Status Pages - Toronto | Funcțional |
| Status Statusio Status Notifications - Email | Funcțional |
| Status Statusio Status Notifications - Webhook | Funcțional |
Incidentele oficiale, semnalele timpurii și rapoartele comunitare sunt identificate separat. Semnalele timpurii acoperă doar ultimele 24 de ore. Datele folosesc fusul tău orar.
| Incident | Durată | ÎnceputUTC | Confirmare oficială | Severitate |
|---|---|---|---|---|
| 0m | Da | Minor | ||
| 0m | Da | Major | ||
| 0m | Da | Major | ||
| 0m | Da | Major | ||
| 0m | Da | Major | ||
| 0m | Da | Major | ||
| 0m | Da | Major | ||
| 0m | Da | Major |
Uptimus monitorizează Statusio prin sursa oficială de status și normalizează incidentele, ferestrele de mentenanță și starea componentelor într-un status unitar.
Această pagină include în prezent 29 componente monitorizate, 10 incidente indexate, 2 ferestre de mentenanță și 1 zile de istoric cunoscut.
Uptimus este un serviciu independent și nu este afiliat cu Statusio. Un status sănătos nu garantează că fiecare utilizator, dispozitiv sau regiune este neafectată.
Primești notificări când Statusio sau una dintre componentele monitorizate raportează o întrerupere majoră ori o problemă critică. Alertele pot fi trimise prin canalele activate în workspace, inclusiv email, push și integrările configurate. Istoricul disponibil conține 10 incidente indexate, oferind fiecărei alerte context dincolo de statusul actual. Un incident recent indexat a fost „Incorrect Metric Failure Notifications”.
Primești alerte despre performanță degradată, impact parțial și incidente mai mici care nu reprezintă o întrerupere completă. Uptimus monitorizează în prezent 29 componente Statusio: Public Status Pages - US-East, Public Status Pages - US-West, Public Status Pages - Ireland, Public Status Pages - Toronto. Alertele pot fi trimise prin canalele activate în workspace, inclusiv email, push și integrările configurate.
Planned work published by the official provider.
February 10, 2026 21:40 UTC Investigating - On February 10, AWS experienced DNS resolution errors (NXDOMAIN responses) affecting a subset of CloudFront distributions globally. During this period, AWS also reported delays in propagating certain configuration changes, including DNS, TLS-related updates, and cache invalidations. While we did not observe broad impact across the status pages we actively monitor, based on AWS reporting and customer feedback, some custom domains may have experienced brief DNS resolution failures during the affected window. Additionally, some cache invalidations may have been delayed, which could have temporarily prevented recent incident or maintenance updates from appearing immediately on certain status pages. This issue originated from an upstream AWS CloudFront service disruption. February 11, 2026 04:18 UTC Resolved - AWS mitigated the DNS resolution errors and fully resolved the CloudFront configuration change propagation and cache invalidation delays by 04:18 UTC on February 11. All related AWS services are operating normally. Status.io infrastructure and monitoring systems continued operating normally throughout the event. Any delayed cache invalidations have since been processed, and status pages should now reflect the correct state.
Started 11 feb. 2026, 04:18 UTC · Ongoing
February 3, 2026 16:15 UTC Identified - We’ve identified a production change deployed yesterday that could prevent some scheduled maintenance events from appearing on status pages with more than 1,000 total maintenance events. This issue is limited to display behavior only and does not affect maintenance execution or underlying system functionality. We are rolling back the change in production. February 3, 2026 16:50 UTC Monitoring - The rollback has been deployed and we are monitoring to confirm that maintenance events are displaying correctly across all status pages. We’ll post a final update once monitoring is complete and the incident is resolved. February 3, 2026 17:50 UTC Resolved - Monitoring has confirmed that maintenance events are now displaying correctly across all status pages following the rollback. This issue was limited to display behavior only and affected status pages with a large number of maintenance events (over 1,000). No maintenance schedules or underlying system functionality were affected. The incident is now resolved. We are reviewing the change that caused the issue to reduce the risk of similar issues in the future.
Started 3 feb. 2026, 17:50 UTC · Ongoing
Paginile publice Downdetector se bazează în principal pe rapoartele utilizatorilor. Uptimus combină activitatea comunității cu incidentele oficiale, ferestrele de mentenanță și starea componentelor atunci când sursa le publică.
| Criterii de comparație | Uptimus | Downdetector |
|---|---|---|
| Rapoarte comunitare despre problemele Statusio | Inclus | Inclus |
| Baseline adaptiv care separă rapoartele izolate de o întrerupere extinsă | Inclus | Inclus |
| Activitatea rapoartelor din 24 de ore și harta regională | Inclus | Inclus |
| Un singur spațiu pentru website-uri, provideri de status, jocuri Steam și aplicații sau jocuri Android | Inclus | Produs separat |
| Alerte prin e-mail, push și webhook din același spațiu de lucru | Inclus | Produs separat |
| Actualizări oficiale ale incidentelor și cronologia statusului Statusio | Inclus | Bazat pe rapoarte |
| Starea componentelor și ferestrele de mentenanță păstrate separat | Inclus | Limitat pe paginile publice |
Statusul oficial curent al Statusio nu poate fi verificat. Ultima observație stocată de la furnizor indica funcționare normală. Nu a fost înregistrat niciun raport despre Statusio în ultimele 24 de ore. Ultima verificare oficială: .
Evaluează acest serviciu
Încă nu există evaluări
Împărtășește-ți gândurile despre Statusio
Fii primul care comentează!
Descoperă alte servicii populare și starea lor actuală
