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

Airwallex status

Airwallex · 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
21
Retained
21
Affected retained
0
Projection scope: complete · 21 retained of 21 reported components across 3 source groups.
Onboarding Group: Product Operational
Web App Group: System Operational
Hong Kong Group: Data center Operational
Mobile App Group: System Operational
Connected Accounts Group: Product Operational
Singapore Group: Data center Operational
Global Accounts Group: Product Operational
Login & 2FA Group: System Operational
Netherlands Group: Data center Operational
Linked Accounts Group: Product Operational
API Gateway Group: System Operational
US East Group: Data center Operational
Payments Group: Product Operational
Notifications & Webhooks Group: System Operational
Billing Group: Product Operational
Sandbox Group: System Operational
Issuing Group: Product Operational
Transactional FX Group: Product Operational
Payouts Group: Product Operational
Balances & Transactions Group: Product Operational
Showing 20 of 21 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 · 421.84 ms feed latency
Operational
HTTP 200 · 172.33 ms feed latency
Operational
HTTP 200 · 259.24 ms feed latency
Operational
HTTP 200 · 328.44 ms feed latency
Operational
HTTP 200 · 363.88 ms feed latency
Operational
HTTP 200 · 292.74 ms feed latency
Operational
HTTP 200 · 244.75 ms feed latency
Operational
HTTP 200 · 351.96 ms feed latency
Operational
HTTP 200 · 435.59 ms feed latency
Operational
HTTP 200 · 284.4 ms feed latency

Collection details

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