Canva · Operational
Observed by INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

Canva status

Canva · Atlassian Statuspage
Operational
Atlassian Statuspage reports All Systems Operational.
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

No active incidents were included in this vendor report.

Maintenance

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

Component health

Reported
35
Retained
35
Affected retained
0
Projection scope: complete · 35 retained of 35 reported components across 5 source groups.
Downloading designs Group: Designs Operational
Android app Group: Mobile and Desktop Applications Operational
Administration and settings Operational
Publishing websites Group: Publish and Scheduling Operational
Canva AI Connector Group: Canva AI Platform Operational
Admin API Group: Apps and Integrations Operational
Editing designs Group: Designs Operational
iOS app Group: Mobile and Desktop Applications Operational
Apps Group: Apps and Integrations Operational
Billing and subscriptions Operational
Scheduling posts Group: Publish and Scheduling Operational
iPad app Group: Mobile and Desktop Applications Operational
Help and support Operational
Apps SDK Group: Apps and Integrations Operational
Importing designs Group: Designs Operational
Home page Operational
macOS app Group: Mobile and Desktop Applications Operational
Blackboard Group: Apps and Integrations Operational
Offline designs Group: Designs Operational
Login and signup Operational
Showing 20 of 35 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 · 306.75 ms feed latency
Operational
HTTP 200 · 434.88 ms feed latency
Operational
HTTP 200 · 567.68 ms feed latency
Operational
HTTP 200 · 417.29 ms feed latency
Operational
HTTP 200 · 282.93 ms feed latency
Operational
HTTP 200 · 358.45 ms feed latency
Operational
HTTP 200 · 472.88 ms feed latency
Operational
HTTP 200 · 514.22 ms feed latency
Operational
HTTP 200 · 471.11 ms feed latency
Operational
HTTP 200 · 556.65 ms feed latency

Collection details

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