Last checked
Hosted status pages for transparent incident communication.
Experiencing an issue?
Statusioは落ちていますか?
Maintenance
Share your experience to help others stay informed.
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Loading reports… · Last 24 hours
Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
| Start | End | Reports | Status |
|---|
Official status checked
Statusio has active maintenance
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 outage reports in the last 24 hours.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 0m | Yes | Major | ||
| 0m | Yes | Major | ||
| 0m | Yes | Major | ||
| 0m | Yes | Major | ||
| 0m | Yes | Major | ||
| 0m | Yes | Major | ||
| 0m | Yes | Major | ||
| 0m | Yes | Major |
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 2026年2月11日 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.
Statusioについてのあなたの考えを共有してください
最初のコメントを残しましょう!
Uptimus は公式ステータス情報から Statusio を監視し、障害、メンテナンス、コンポーネントの状態を共通のステータスに正規化します。
このページには現在、29 件のコンポーネント、9 件の障害、2 件のメンテナンス、2 日分の履歴があります。
Uptimus は独立したサービスで、Statusio とは提携していません。正常表示でも、すべての利用者、端末、地域に問題がないことを保証するものではありません。
Statusio または監視対象コンポーネントで重大な障害が報告されたときに通知します。 通知はメール、プッシュ、設定済み連携など、ワークスペースで有効なチャネルに配信できます。 利用可能な履歴には 9 件の障害があり、現在の状態を超えた背景を提供します。 最近記録された障害は「Deploy Version 1.8.8」です。
性能低下、部分的な影響、全面停止ではない小規模な障害について通知します。 Uptimus は現在 Statusio の 29 コンポーネントを追跡しています: Public Status Pages - US-East, Public Status Pages - US-West, Public Status Pages - Ireland, Public Status Pages - Toronto。 通知はメール、プッシュ、設定済み連携など、ワークスペースで有効なチャネルに配信できます。
Downdetector の公開ページは主にユーザー報告を中心としています。Uptimus は、提供元が公開する公式インシデント、メンテナンス、コンポーネント状態も組み合わせます。
| 比較基準 | Uptimus | Downdetector |
|---|---|---|
| Statusio のコミュニティ障害報告 | 利用可能 |
The official status page for Statusio reports normal operation. 0 reports were recorded for Statusio in the last 24 hours. Last official check: .
Started 2026年2月3日 17:50 UTC · Ongoing
| 利用可能 |
| 個別の報告と広範な障害を区別する適応型ベースライン | 利用可能 | 利用可能 |
|---|
| 24時間の報告推移と地域別障害マップ | 利用可能 | 利用可能 |
|---|
| Webサイト、公式ステータス、Steam、Androidアプリとゲームを1つのワークスペースで管理 | 利用可能 | 別製品 |
|---|
| 同じワークスペースからメール、プッシュ、Webhook通知 | 利用可能 | 別製品 |
|---|
| Statusio の公式インシデント更新とステータスタイムライン | 利用可能 | ユーザー報告中心 |
|---|
| コンポーネント状態とメンテナンスを分けて表示 | 利用可能 | 公開ページでは限定的 |
|---|
Rate this service
No reviews yet