Vendor-reported status observed by INTERNETMON
Make status
Make · 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
30
Retained
30
Affected retained
0
Projection scope: complete · 30 retained of 30 reported components across 4 source groups.
eu1.make.com
Group: Website
Operational
eu1.make.com
Group: Responsive Webhooks
Operational
eu1.make.com
Group: Scenario Executions
Operational
eu1.make.com
Group: Apps
Operational
eu2.make.com
Group: Website
Operational
eu2.make.com
Group: Responsive Webhooks
Operational
eu2.make.com
Group: Scenario Executions
Operational
eu2.make.com
Group: Apps
Operational
us1.make.com
Group: Website
Operational
us1.make.com
Group: Responsive Webhooks
Operational
us1.make.com
Group: Scenario Executions
Operational
us1.make.com
Group: Apps
Operational
us2.make.com
Group: Website
Operational
us2.make.com
Group: Responsive Webhooks
Operational
us2.make.com
Group: Scenario Executions
Operational
us2.make.com
Group: Apps
Operational
eu1.make.celonis.com
Group: Website
Operational
eu1.make.celonis.com
Group: Responsive Webhooks
Operational
eu1.make.celonis.com
Group: Scenario Executions
Operational
eu1.make.celonis.com
Group: Apps
Operational
Showing 20 of 30 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 · 312.95 ms feed latency
Operational
HTTP 200 · 10385.57 ms feed latency
Operational
HTTP 200 · 234.58 ms feed latency
Operational
HTTP 200 · 235.62 ms feed latency
Operational
HTTP 200 · 359.26 ms feed latency
Operational
HTTP 200 · 221.68 ms feed latency
Operational
HTTP 200 · 173.04 ms feed latency
Operational
HTTP 200 · 226.14 ms feed latency
Operational
HTTP 200 · 324.59 ms feed latency
Operational
HTTP 200 · 170.67 ms feed latency
Collection details
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
189.65 ms
JSON source