Kinsta · Degraded
Observed by INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

Kinsta status

Kinsta · Atlassian Statuspage
Degraded
Atlassian Statuspage reports Partially Degraded Service.
Official service health, components and incident updates
Checked Poll cadence every 60 seconds Feed state fresh
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.

Active incidents

Mykinsta file manager issue with uploading larger files

We are still investigating the issue. Thank you for your patience.

Status investigating Impact degraded Updated

Maintenance

No active or upcoming maintenance was included in this vendor report.

Component health

Reported
56
Retained
56
Affected retained
1
Projection scope: complete · 56 retained of 56 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 Degraded
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
Delhi, India data center Operational
Showing 20 of 56 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.

Degraded
HTTP 200 · 277.03 ms feed latency
Degraded
HTTP 200 · 514.24 ms feed latency
Degraded
HTTP 200 · 231.47 ms feed latency
Degraded
HTTP 200 · 426.17 ms feed latency
Degraded
HTTP 200 · 409.64 ms feed latency
Degraded
HTTP 200 · 441.9 ms feed latency
Degraded
HTTP 200 · 444.18 ms feed latency
Degraded
HTTP 200 · 532.69 ms feed latency
Degraded
HTTP 200 · 512.69 ms feed latency
Degraded
HTTP 200 · 452.78 ms feed latency

Collection details

Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
302.52 ms