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

Coinbase status

Coinbase · 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
169
Retained
100
Affected retained
0
Projection scope: complete · 100 retained of 169 reported components across 5 source groups · bounded/truncated source projection.
Coinbase - Website Operational
Bitcoin Group: Digital Currencies Operational
Credit & Debit Cards Group: Payment Methods Operational
Proof of Address Group: User Proofing Operational
Dapp wallet Group: Dapp Operational
Wallets Group: Coinbase Developer Platform Operational
US Bank Accounts Group: Payment Methods Operational
Coinbase - Mobile Operational
ID verification Group: User Proofing Operational
Bitcoin Cash Group: Digital Currencies Operational
Dapp browser Group: Dapp Operational
Payments Group: Coinbase Developer Platform Operational
Ethereum Group: Digital Currencies Operational
US Wires Group: Payment Methods Operational
ID authentication (Japan) Group: User Proofing Operational
Coinbase - Advanced Trade Operational
Stablecoins Group: Coinbase Developer Platform Operational
Ethereum Classic Group: Digital Currencies Operational
US Derivatives Operational
Trading Group: Coinbase Developer Platform Operational
Showing 20 of 100 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 · 142.81 ms feed latency
Operational
HTTP 200 · 121.22 ms feed latency
Operational
HTTP 200 · 124.58 ms feed latency
Operational
HTTP 200 · 181.53 ms feed latency
Operational
HTTP 200 · 113.17 ms feed latency
Operational
HTTP 200 · 108.48 ms feed latency
Operational
HTTP 200 · 114.46 ms feed latency
Operational
HTTP 200 · 125.81 ms feed latency
Operational
HTTP 200 · 113.82 ms feed latency
Operational
HTTP 200 · 117.3 ms feed latency

Collection details

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