Vendor-reported status observed by INTERNETMON
Kinsta status
Kinsta · 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
58
Retained
58
Affected retained
0
Projection scope: complete · 58 retained of 58 reported components.
Affiliate Dashboard
Operational
Cloudflare Integration
Operational
Kinsta.com
Operational
Kinsta API
Operational
Kinsta CDN
Operational
Kinsta DNS
Operational
Kinsta support system
Operational
MyKinsta
Operational
MyKinsta analytics servers
Operational
Outbound Email System
Operational
Amsterdam, Netherlands data center
Operational
Ashburn, Virginia, US data centers
Operational
Batam, Indonesia data center
Operational
Bogotá, Colombia data center
Operational
Changhua County, Taiwan data center
Operational
Chicago, Illinois, US data center
Operational
Columbus, Ohio, US data center
Operational
Council Bluffs, Iowa, US data center
Operational
Dallas, Texas, US data center
Operational
Dammam, Saudi Arabia data center
Operational
Showing 20 of 58 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 · 175.61 ms feed latency
Operational
HTTP 200 · 294.25 ms feed latency
Operational
HTTP 200 · 375.66 ms feed latency
Operational
HTTP 200 · 289.83 ms feed latency
Operational
HTTP 200 · 334.49 ms feed latency
Operational
HTTP 200 · 186.63 ms feed latency
Operational
HTTP 200 · 252.81 ms feed latency
Operational
HTTP 200 · 136.02 ms feed latency
Operational
HTTP 200 · 15336.08 ms feed latency
Operational
HTTP 200 · 166.34 ms feed latency
Collection details
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
424.21 ms
JSON source