Skip to content
PulseWatchOUTAGE.INTEL
Circle (USDC) logo

Other

Is Circle (USDC) down right now?

Vendor-reported issueOfficial status last polled Sep 28, 2026 09:13 UTCwww.circle.comOfficial status page

Are you on the Circle (USDC) team and see something inaccurate? Report it to us. We respond within one business day.

Is Circle (USDC) down right now?

Vendor-reported issue. Circle (USDC): Noble CCTP Mainnet Maintenance Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

Status as of Sep 28, 2026 10:24 UTC

Vendor-reported issueVendor-reported issue

Circle (USDC): vendor reports an issue

As of Sep 28, 2026 10:24 UTC

Noble CCTP Mainnet Maintenance Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

Recent qualified checks passed for CCTP mainnet public signing-key registry API. These results cover only those operations; they do not establish overall service health.

Reports 24h

0

Last incident

Sep 27, 2026 17:02 UTC

Trend

0/15m

Monitoring

Operation checks passing

Observed health

100/100

3 of 3 assessed samples succeeded within their latency target.

6/6 responses validated in the last 15 minutes. 3 successful samples have no qualified latency target.

Evidence strength

Vendor-reported

An official notice is available; independent agreement is unproven.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Circle (USDC).

19

Incident days

11

No recorded incident

388h

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Circle (USDC). Hover a day for detail.

Aug 30Sep 4Sep 9Sep 14Sep 19Sep 2401234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

19

Days with incidents

2 incidents

Busiest day

388h

Recorded duration

Report volume

0 reports in last 24H

10:15 AM01:45 PM05:15 PM08:45 PM12:15 AM03:45 AM07:15 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Circle (USDC) outage on September 27 A 1h 35m disruption

Sep 27, 03:26 PM → Sep 27, 05:02 PM · 1h 35m · high

A high-severity incident affecting Circle (USDC) was detected through automated signals, including the vendor's status page. The disruption began on September 27, 2026, at 15:26 UTC. The incident was resolved on September 27, 2026, at 17:02 UTC.

Peak reports
0
in 15 min
Total reports
0
during outage
Duration
1h 35m
until recovery

Impact

During the 1 hour and 35 minute high-severity incident, the Circle (USDC) service experienced a disruption. This incident was detected solely through automated monitoring and the vendor's status page. No user-reported data, including specific issue types or affected regions, was collected for this incident.

Outage timeline

  1. Sep 27, 03:26 PM

    PulseWatch detected the incident from automated vendor and probe signals (high severity)

  2. Sep 27, 03:26 PM

    Status updated: possible issue

  3. Sep 27, 05:02 PM

    Signals cleared — incident resolved

Official updates

  1. Sep 27, 03:26 PM

    Circle (USDC) status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals.

Reliability

Detected by PulseWatch

30-day uptime

44.2%

90-day uptime

70.8%

Calculated from Circle (USDC)'s detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
Possible issueHigh

Circle (USDC): the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Circle (USDC) or have an alert rule on it can be alerted, labelled vendor-reported.

live

9/28/2026, 3:00:47 AM · 7h 24m

03:00 AM10:24 AM (live)
Detection9/28/2026, 3:00:47 AM · 7h ago

Detected — high severity

Circle (USDC): the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Circle (USDC) or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedHigh

Circle (USDC): the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Circle (USDC) or have an alert rule on it can be alerted, labelled vendor-reported.

9/27/2026, 3:26:50 PM · 1h 35m

03:26 PM05:02 PM
Detection9/27/2026, 3:26:50 PM · 18h ago

Detected — high severity

Circle (USDC): the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Circle (USDC) or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedHigh

Circle (USDC): the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Circle (USDC) or have an alert rule on it can be alerted, labelled vendor-reported.

9/24/2026, 3:16:58 PM · 3d 0h

03:16 PM03:21 PM
Detection9/24/2026, 3:16:58 PM · 3d ago

Detected — high severity

Circle (USDC): the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Circle (USDC) or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedHigh

Circle (USDC): the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Circle (USDC) or have an alert rule on it can be alerted, labelled vendor-reported.

9/21/2026, 3:09:40 PM · 3d 0h

03:09 PM03:11 PM
Detection9/21/2026, 3:09:40 PM · 6d ago

Detected — high severity

Circle (USDC): the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Circle (USDC) or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedHigh

Circle (USDC): the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Circle (USDC) or have an alert rule on it can be alerted, labelled vendor-reported.

9/20/2026, 2:51:52 PM · 13h 10m

02:51 PM04:02 AM
Detection9/20/2026, 2:51:52 PM · 7d ago

Detected — high severity

Circle (USDC): the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Circle (USDC) or have an alert rule on it can be alerted, labelled vendor-reported.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Circle (USDC) enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Vendor-reported issue
Monitoring
Vendor-reported issue: Noble CCTP Mainnet Maintenance. Affected scope is described in the vendor notice; service-wide impact is not established.
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

www.circle.com