Vendor-reported status observed by INTERNETMON
Builder.io status
Builder.io · Atlassian Statuspage
Atlassian Statuspage reports All Systems Operational.
Official service health, components and incident updates
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.
Active incidents
No active incidents were included in this vendor report.
Maintenance
No active or upcoming maintenance was included in this vendor report.
Component health
Reported
31
Retained
31
Affected retained
0
Projection scope: complete · 31 retained of 31 reported components across 4 source groups.
Content Delivery APIs
Group: Publish
Operational
AWS cloudfront
Group: CDN
Operational
Google Cloud Platform Google Cloud Storage
Group: Cloud Providers
Operational
Figma Import
Group: Fusion
Operational
Google Cloud Platform Google Cloud Networking
Group: Cloud Providers
Operational
Fastly Toronto (YYZ)
Group: CDN
Operational
Content Asset CDN
Group: Publish
Operational
Code Generation
Group: Fusion
Operational
Content Management and Web App
Group: Publish
Operational
Google Cloud Platform Identity & Access Management
Group: Cloud Providers
Operational
Fastly Chicago (CHI)
Group: CDN
Operational
Projects
Group: Fusion
Operational
Google Cloud Platform Google App Engine
Group: Cloud Providers
Operational
Fastly Boston (BOS)
Group: CDN
Operational
Google Cloud Platform Google BigQuery
Group: Cloud Providers
Operational
Fastly Atlanta (ATL)
Group: CDN
Operational
Fastly Munich (MUC)
Group: CDN
Operational
Google Cloud Platform Cloud Filestore
Group: Cloud Providers
Operational
Fastly London (LON)
Group: CDN
Operational
Fly.io Machines API
Group: Cloud Providers
Operational
Showing 20 of 31 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.
Recent observed status changes and checkpoints
These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.
Operational
HTTP 200 · 187.34 ms feed latency
Operational
HTTP 200 · 326.02 ms feed latency
Operational
HTTP 200 · 274.87 ms feed latency
Operational
HTTP 200 · 99.4 ms feed latency
Operational
HTTP 200 · 312.6 ms feed latency
Operational
HTTP 200 · 168.22 ms feed latency
Operational
HTTP 200 · 333.9 ms feed latency
Operational
HTTP 200 · 446.08 ms feed latency
Operational
HTTP 200 · 295.25 ms feed latency
Operational
HTTP 200 · 275.98 ms feed latency
Collection details
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
227.95 ms
JSON source