VulnPulse

クラウド・サービスの障害情報

10月21日(水)昨日

  • 解決済み08:53障害・メンテナンスFly.ioFly.io Status

    Capacity issues in GRU region

    Status: Resolved We have added host capacity to the region. Machine creates, starts and remote builds in GRU should now be functioning as normal. Affected components GRU - Sao Paulo, Brazil (Operational) Remote Builds (Operational)

10月17日(土)

  • 解決済み14:15障害・メンテナンスFly.ioFly.io Status

    Platform Wide Rolling Host Reboots

    Status: Resolved All host restarts have been completed and the platform is operating normally. A small number of hosts remain degraded or offline for apps and for MPG. Those impacted can see further updates on the personalized status page viewable at https://fly.io/status Affected components Management Plane - AMS (Operational) SJC - San Jose, California (US) (Operational) Management Plane - NRT (Operational) DFW - Dallas, Texas (US) (Operational) GRU - Sao Paulo, Brazil (Operational) Management Plane - GRU (Operational) ARN - Stockholm, Sweden (Operational) LAX - Los Angeles, California (US)…

  • 解決済み04:24障害・メンテナンスFly.ioFly.io Status

    Fly-metrics.net Grafana Dashboard Outage

    Status: Resolved The fly-metrics.net: https://fly-metrics.net hosted Grafana and log search instance is now fully reachable. Affected components Logs (Operational) Metrics (Operational)

10月15日(木)

  • 解決済み20:33障害・メンテナンスFly.ioFly.io Status

    Elevated errors creating apps and managing secrets

    Status: Resolved Between 06:40 and 09:50 UTC some app creation and secrets requests failed or timed out. Running apps and Machines were not affected. Affected components Deployments (Operational) Customer Applications (Operational) Machines API (Operational)

  • 解決済み11:35障害・メンテナンスFly.ioFly.io Status

    Partial FRA network issues

    Status: Resolved Subset of hosts in FRA were unavailable due to provider network outage which lasted around 10 minutes

10月13日(火)

10月12日(月)

  • 解決済み08:30障害・メンテナンスFly.ioFly.io Status

    Sprite hosting outage

    Status: Resolved From approximately 2026-10-11 23:30 UTC through 2026-10-12 00:45 UTC some or all hosted sprites on the *.sprites.app subdomain were unavailable due to a certificate error. As of 00:45 UTC this incident has been resolved.

10月9日(金)

10月8日(木)

  • 解決済み15:00障害・メンテナンスFly.ioFly.io Status

    LHR network issues

    Status: Resolved This incident has been resolved. Affected components LHR - London, United Kingdom (Operational)

10月6日(火)

  • 解決済み21:02障害・メンテナンスFly.ioFly.io Status

    Impaired IPv6 connectivity in ORD

    Status: Resolved IPv6 upstream issue was solved. Affected components ORD - Chicago, Illinois (US) (Operational) Customer Applications (Operational)

10月3日(土)

  • 解決済み17:57障害・メンテナンスFly.ioFly.io Status

    Partial outage in AMS

    Status: Resolved All impacted services are operational now. Affected components AMS - Amsterdam, Netherlands (Operational) Management Plane - AMS (Operational)

10月1日(木)

9月30日(水)

  • 解決済み04:30障害・メンテナンスFly.ioFly.io Status

    GRU Networking Issues

    Status: Resolved We observed networking issues affecting a subset of our hosts in GRU from 19:37 UTC through 19:59 UTC. This affected platform operations requiring leases, private networking, and internet connectivity to some endpoints.

9月27日(日)

9月25日(金)

9月24日(木)

  • 解決済み16:22障害・メンテナンスFly.ioFly.io Status

    Upstash unavailability in FRA region

    Status: Resolved Impact From about 12:00 to 13:05 UTC, some clients got connection timeouts to their Redis databases. Affected were databases hosted in fra or gig, and clients whose connections were routed through fra or gig, even if their database is hosted in another region. What happened During a planned rolling upgrade, replicas in fra and gig did not finish draining and were left out of service. They were returned to Fly routing before they were ready to accept connections. Connections routed to them then timed out. What we're changing • We will be adding tooling to return a replica to s…

  • 解決済み11:12障害・メンテナンスFly.ioFly.io Status

    Partial Sprites outage

    Status: Resolved This incident has been resolved. Affected components Sprites (Operational)

  • 解決済み00:23障害・メンテナンスFly.ioFly.io Status

    Elevated private networking errors

    Status: Resolved This incident has been resolved. Affected components Customer Applications (Operational)

9月23日(水)

9月15日(火)

9月13日(日)

  • 解決済み07:12障害・メンテナンスFly.ioFly.io Status

    Network issues in US West Coast

    Status: Resolved This incident has been resolved. Affected components LAX - Los Angeles, California (US) (Operational) SJC - San Jose, California (US) (Operational)

9月3日(木)

  • 解決済み09:41障害・メンテナンスFly.ioFly.io Status

    Sprites API Partial Outage

    Status: Resolved This incident has been resolved. Affected components Sprites (Operational)

  • 解決済み00:57障害・メンテナンスFly.ioFly.io Status

    Upstream network issues

    Status: Resolved This incident has been resolved. Affected components LAX - Los Angeles, California (US) (Operational) SJC - San Jose, California (US) (Operational)

9月2日(水)

9月1日(火)

  • 解決済み00:30障害・メンテナンスFly.ioFly.io Status

    HTTP/2 traffic disruptions

    Status: Resolved A configuration update caused temporary failures for incoming HTTP/2 traffic for Fly Machines located on a subset of hosts for a few minutes. This incident has since been resolved. Managed Postgres depends on HTTP/2 and some control plane ops may have been affected as well. However, downstream Postgres connections were unlikely to have been affected by this since they do not use the HTTP2 handler.

8月31日(月)

  • 解決済み17:10障害・メンテナンスFly.ioFly.io Status

    Packet loss in ORD

    Status: Resolved This incident has been resolved. Affected components ORD - Chicago, Illinois (US) (Operational)

  • 解決済み07:45障害・メンテナンスFly.ioFly.io Status

    Sprite deletion jobs failing

    Status: Resolved We saw Sprite deletion jobs failing between 21:18 and 22:05 UTC. This issue has been resolved.

8月29日(土)

8月28日(金)

  • 解決済み19:22障害・メンテナンスFly.ioFly.io Status

    Increased packet loss

    Status: Resolved This incident has been resolved. Affected components Customer Applications (Operational)

8月27日(木)

8月24日(月)

8月23日(日)

8月21日(金)

  • 解決済み04:30障害・メンテナンスFly.ioFly.io Status

    Temporary DNS resolution failure

    Status: Resolved A BGP configuration error caused our Anycast DNS to route to some nodes without the proper DNS infrastructure. The issue was temporary and was resolved as soon as we removed that node from BGP.

8月20日(木)

8月19日(水)

  • 解決済み09:00障害・メンテナンスFly.ioFly.io Status

    6PN Networking issue in YYZ

    Status: Resolved 6PN networking issues between some machines in YYZ during a rollout which was rolled back once we noticed errors. During this time some machines were unable to talk to internal resources like other DBs, other apps or MPG clusters.

8月18日(火)

  • 解決済み00:41障害・メンテナンスFly.ioFly.io Status

    No capacity in ARN

    Status: Resolved The capacity issue in the ARN region has been resolved. Affected components Deployments (Operational)

8月15日(土)

8月14日(金)

  • 解決済み04:41障害・メンテナンスFly.ioFly.io Status

    IPv6 Networking Issues

    Status: Resolved This incident has been resolved. Affected components Customer Applications (Operational)

8月9日(日)

8月6日(木)

8月5日(水)

8月4日(火)

  • 解決済み03:50障害・メンテナンスFly.ioFly.io Status

    Inbound connection failure to Fly Apps

    Status: Resolved A BGP misconfiguration while provisioning new edge capacity caused most traffic from Europe endpoints to be dropped, between 14:50 UTC and 15:02 UTC. The misconfiguration has been fixed and we are implementing safeguards against this kind of issue in the future.

8月2日(日)

8月1日(土)

  • 解決済み05:11障害・メンテナンスFly.ioFly.io Status

    Capacity issues in CDG

    Status: Resolved This incident has been resolved. Affected components CDG - Paris, France (Operational)

7月31日(金)

7月29日(水)

  • 解決済み22:26障害・メンテナンスFly.ioFly.io Status

    Increased API latency

    Status: Resolved This incident has been resolved. Affected components Machines API (Operational) Dashboard (Operational) Deployments (Operational)