Skip to content

Active service issues

Slow responses, errors, partial outages, and issues affecting individual components or regions. Refreshed every minute.

62 services have issues in the available evidence: PulseWatch findings, corroborated incidents, or vendor reports. Our measurements do not need vendor confirmation. Corroborated means independent sources agree on the issue and scope. Each service is counted once, even when several sources or components are affected. Services that show the same notice from one shared vendor status page are listed together: 60 services show 51 vendor notices.

Last refreshed Oct 10, 1:07 PM. 48 services checked in this feed; 32 matched to the catalog.

C Spire

Community reports indicate possible problems with C Spire.

Collected Oct 10, 12:58 PM

Community signal; independent corroboration is not yet established.

Catalog mapping pending.

View community report
DailyPay

Community reports indicate possible problems with DailyPay.

Collected Oct 10, 12:58 PM

Community signal; independent corroboration is not yet established.

Catalog mapping pending.

View community report
DirecTV

Community reports indicate possible problems with DirecTV.

Collected Oct 10, 12:58 PM

Community signal; independent corroboration is not yet established.

Catalog mapping pending.

View community report
DoorDash logo
DoorDash

Community reports indicate possible problems with DoorDash.

Collected Oct 10, 12:58 PM

Community signal; independent corroboration is not yet established.

View community report
Florida Power & Light

Community reports indicate possible problems with Florida Power & Light.

Collected Oct 10, 12:58 PM

Community signal; independent corroboration is not yet established.

Catalog mapping pending.

View community report
Huntington Bank logo
Huntington Bank

Community reports indicate possible problems with Huntington Bank.

Collected Oct 10, 12:58 PM

Community signal; independent corroboration is not yet established.

View community report
Mediacom logo
Mediacom

Community reports indicate possible problems with Mediacom.

Collected Oct 10, 12:58 PM

Community signal; independent corroboration is not yet established.

View community report
Point Broadband

Community reports indicate possible problems with Point Broadband.

Collected Oct 10, 12:58 PM

Community signal; independent corroboration is not yet established.

Catalog mapping pending.

View community report
Skyward

Community reports indicate possible problems with Skyward.

Collected Oct 10, 12:58 PM

Community signal; independent corroboration is not yet established.

Catalog mapping pending.

View community report
Straight Talk

Community reports indicate possible problems with Straight Talk.

Collected Oct 10, 12:58 PM

Community signal; independent corroboration is not yet established.

Catalog mapping pending.

View community report
WOW

Community reports indicate possible problems with WOW.

Collected Oct 10, 12:58 PM

Community signal; independent corroboration is not yet established.

Catalog mapping pending.

View community report
Walmart logo
Walmart

Community reports indicate possible problems with Walmart.

Collected Oct 10, 12:58 PM

Community signal; independent corroboration is not yet established.

View community report
YouTube TV logo
YouTube TV

Community reports indicate possible problems with YouTube TV.

Collected Oct 10, 12:58 PM

Community signal; independent corroboration is not yet established.

View community report
itch.io logo
itch.io

Community reports indicate possible problems with itch.io.

Collected Oct 10, 12:58 PM

Community signal; independent corroboration is not yet established.

View community report

Services with issues

PulseWatch findings and vendor reports appear together, with each service counted once. Services that show the same vendor notice from one shared status page are listed together as one entry. Slow responses, errors, and component or regional issues do not mean an entire service is down.

62 services shown in 53 entries

  • One vendor notice on 2 services: Anthropic, Claude

    Major issue
    Vendor-reported

    Anthropic: Elevated errors on platform.claude.com

    Affected scope is described in the vendor notice; service-wide impact is not established.

    official status feed · checked 3m ago · vendor posted 2d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    These services share one vendor status page, and each shows this same notice, so it is listed once.

    Anthropic

    Detected byVendor statement

    Source: vendor:status.anthropic.com

    Independent origins
    1
    Corroborating signals
    1 evidence row
    Vendor claim
    a major-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 7, 2026 13:28 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

    Claude

    Detected byVendor statement

    Source: status.anthropic.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a major-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 7, 2026 13:40 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Bandwidth logo

    Bandwidth

    Major issue
    Vendor-reported

    Bandwidth Local Market Impairment - 122 - Manchester, NH

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 1h ago · vendor posted 1d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: status.bandwidth.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a critical-impact incident
    Our evidence-based assessment
    moderategraded from this incident’s evidence · Oct 9, 2026 00:05 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Circle (USDC) logo

    Circle (USDC)

    Major issue
    Vendor-reported

    USDC on XRP

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 56m ago · vendor posted 21h ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: status.circle.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a major-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 9, 2026 18:12 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    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.

  • Cloudflare logo

    Cloudflare

    Major issue
    Vendor-reported

    Elevated Errors in China Network Colos

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 56m ago · vendor posted 8h ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: www.cloudflarestatus.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 10, 2026 04:36 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    100/100

    2 of 2 assessed samples succeeded within their latency target.

    5/5 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.

  • CloudSigma logo

    CloudSigma

    Major issue
    Vendor-reported

    [ALL] Chat & Ticketing System Unavailable

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 51m ago · vendor posted 12d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: status.cloudsigma.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 10, 2026 04:41 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Datto RMM logo

    Datto RMM

    Major issue
    Vendor-reported

    DattoRMM - All Platforms - MacOS Agent Connectivity Issues

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 51m ago · vendor posted 7d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Drata logo

    Drata

    Major issue
    Vendor-reported

    Some Policy PDF Downloads Missing Appendix Page

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 46m ago · vendor posted 4d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • One vendor notice on 4 services: Elastic, Elastic Cloud, Elastic Observability, Elasticsearch

    Major issue
    Vendor-reported

    Connectivity disruption for AWS Bahrain (me-south-1)

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 46m ago · vendor posted 7mo ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    These services share one vendor status page, and each shows this same notice, so it is listed once.

    Elastic

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

    Elastic Cloud

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

    Elastic Observability

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

    Elasticsearch

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • One vendor notice on 2 services: ESET, ESET PROTECT

    Major issue
    Vendor-reported

    Customers connected via Telia ISP cannot connect to ESET Cloud Services

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 46m ago · vendor posted 3mo ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    These services share one vendor status page, and each shows this same notice, so it is listed once.

    ESET

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

    ESET PROTECT

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Flutterwave logo

    Flutterwave

    Major issue
    Vendor-reported

    [Ghana] Service Alert: Incoming Payments Delays

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 41m ago · vendor posted 2mo ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Genesys logo

    Genesys

    Major issue
    Vendor-reported

    Genesys: Elevated Error Rates - EMEA (UAE)

    Affected scope is described in the vendor notice; service-wide impact is not established.

    official status feed · checked 8m ago · vendor posted 2mo ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • GroqCloud logo

    GroqCloud

    Major issue
    Vendor-reported

    Model Performance or Availability Issue - minimaxai/minimax-m2.7

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 36m ago · vendor posted 3h ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: groqstatus.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a major-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 10, 2026 10:56 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • MongoDB Atlas logo

    MongoDB Atlas

    Major issue
    Vendor-reported

    MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1

    Affected scope is described in the vendor notice; service-wide impact is not established.

    official status feed · checked 8m ago · vendor posted 1mo ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Secoda logo

    Secoda

    Major issue
    Vendor-reported

    Status page lists APAC API: downtime

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 10m ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • One vendor notice on 2 services: Tenable, Tenable Vulnerability Management

    Major issue
    Vendor-reported

    Tenable Vulnerability Management: RBAC Permissions Issue with Custom Roles

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 1m ago · vendor posted 3d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    These services share one vendor status page, and each shows this same notice, so it is listed once.

    Tenable

    Detected byVendor statement

    Source: status.tenable.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a major-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 9, 2026 23:47 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

    Tenable Vulnerability Management

    Detected byVendor statement

    Source: status.tenable.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a major-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 9, 2026 23:47 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • One vendor notice on 2 services: Akamai, Akamai Edge

    Degraded / partial issue
    Vendor-reported

    Origin Server Connectivity Issues with Elevated Errors in APAC Region

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 1h ago · vendor posted 17d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    These services share one vendor status page, and each shows this same notice, so it is listed once.

    Akamai

    Detected byVendor statement

    Source: www.akamaistatus.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 1, 2026 16:36 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

    Akamai Edge

    Detected byVendor statement

    Source: www.akamaistatus.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 1, 2026 17:57 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Anthology Blackboard logo

    Anthology Blackboard

    Degraded / partial issue
    Vendor-reported

    Student Application Unavailable on Citrix - Global

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 1h ago · vendor posted 12d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: status.anthology.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 9, 2026 15:12 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Arctic Wolf logo

    Arctic Wolf

    Degraded / partial issue
    Vendor-reported

    Arctic Wolf Agent Downloads failing

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 1h ago · vendor posted 22h ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: status.arcticwolf.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 8, 2026 20:56 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • One vendor notice on 2 services: ChatGPT, OpenAI

    Degraded / partial issue
    Vendor-reported

    OpenAI: Delayed Costs data in the Compliance API

    Affected scope is described in the vendor notice; service-wide impact is not established.

    official status feed · checked 3m ago · vendor posted 19h ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    These services share one vendor status page, and each shows this same notice, so it is listed once.

    ChatGPT

    Detected byVendor statement

    Source: status.openai.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 9, 2026 18:01 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

    OpenAI

    Detected byVendor statement

    Source: vendor:status.openai.com

    Independent origins
    1
    Corroborating signals
    1 evidence row
    Vendor claim
    a major-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 9, 2026 21:13 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Cisco ThousandEyes logo

    Cisco ThousandEyes

    Degraded / partial issue
    Vendor-reported

    Dashboard widgets showing data for Events datasource are affected in US1 region.

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 1m ago · vendor posted 8h ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: status.thousandeyes.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 9, 2026 08:31 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Clerk logo

    Clerk

    Degraded / partial issue
    Vendor-reported

    Development instances only - Apple rejecting emails

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 56m ago · vendor posted 11d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Cloudflare Zero Trust logo

    Cloudflare Zero Trust

    Degraded / partial issue
    Vendor-reported

    Incorrect geo location for some Cloudflare WARP users

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 51m ago · vendor posted 1mo ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Cloudways logo

    Cloudways

    Degraded / partial issue
    Vendor-reported

    Degradation Impacting Vultr Server Operations

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 51m ago · vendor posted 9d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Coinbase logo

    Coinbase

    Degraded / partial issue
    Vendor-reported

    Delayed Sends and Receives - EGLD (MultiversX)

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 51m ago · vendor posted 21d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    3/3 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.

  • Couchbase Capella logo

    Couchbase Capella

    Degraded / partial issue
    Vendor-reported

    Capella Operations Impacted by GCP us-central1 region capacity issues

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 51m ago · vendor posted 3d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Delta Air Lines logo

    Delta Air Lines

    Degraded / partial issue
    PulseWatch observed

    Server errors measured by PulseWatch checks.

    Scope: measured endpoint · Affected geography not established

    1 independent measurement origin · checked just now

    View our measurements
    • pulsewatch-runtime · availability · observed 10m ago

    Vendor confirmation is not required. These findings describe the measured scope; paging requires independent corroboration.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    Evidence strength

    PulseWatch observed

    1 independent origin.

    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.

  • Fireworks AI logo

    Fireworks AI

    Degraded / partial issue
    Vendor-reported

    Service Degradation for Qwen 3.8 Max

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 41m ago · vendor posted 2h ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: status.fireworks.ai

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 10, 2026 12:21 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • GoCardless logo

    GoCardless

    Degraded / partial issue
    Vendor-reported

    Intermittent ARUDD-8 failures for Nationwide Bank

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 36m ago · vendor posted 15d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • One vendor notice on 2 services: Grafana, Grafana Cloud

    Degraded / partial issue
    Vendor-reported

    IRM Unable to Send SMS to Thailand, Bangladesh, and Austrian Numbers

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 36m ago · vendor posted 4d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    These services share one vendor status page, and each shows this same notice, so it is listed once.

    Grafana

    Detected byVendor statement

    Source: status.grafana.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a major-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 8, 2026 21:37 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

    Grafana Cloud

    Detected byVendor statement

    Source: status.grafana.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a major-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 8, 2026 21:38 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Heap logo

    Heap

    Degraded / partial issue
    Vendor-reported

    Salesforce integration: data-in not syncing

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 36m ago · vendor posted 7d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Kraken logo

    Kraken

    Degraded / partial issue
    Vendor-reported

    Decred (DCR) deposits temporarily unavailable

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 31m ago · vendor posted 21h ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    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.

  • Ledger logo

    Ledger

    Degraded / partial issue
    Vendor-reported

    Stellar (XLM) Mainnet Degraded Service

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 2m ago · vendor posted 2mo ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    100/100

    2 of 2 assessed samples succeeded within their latency target.

    5/5 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.

  • Linode logo

    Linode

    Degraded / partial issue
    Vendor-reported

    Service Issue - Cloud Manager and API

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 26m ago · vendor posted 1d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: status.linode.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 9, 2026 05:07 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    100/100

    2 of 2 assessed samples succeeded within their latency target.

    5/5 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.

  • Matillion logo

    Matillion

    Degraded / partial issue
    Vendor-reported

    Partially Degraded Service

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 26m ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Mercury logo

    Mercury

    Degraded / partial issue
    Vendor-reported

    Failed Investments Wire Transfers Out for Some Customers

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 21m ago · vendor posted 2d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: status.mercury.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 7, 2026 23:10 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Mono logo

    Mono

    Degraded / partial issue
    Vendor-reported

    FCMB Mobile (Authentication Outage)

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 3m ago · vendor posted 17mo ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Qualys logo

    Qualys

    Degraded / partial issue
    Vendor-reported

    IN Platform 1: Performance issues observed on VMDR pages (IM-12904)

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 11m ago · vendor posted 3d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: vendor:status.qualys.com

    Independent origins
    1
    Corroborating signals
    1 evidence row
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 10, 2026 11:17 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • QuickNode logo

    QuickNode

    Degraded / partial issue
    Vendor-reported

    Morph mainnet : Degraded performance in EU region

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 2m ago · vendor posted 4h ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: vendor:status.quicknode.com

    Independent origins
    1
    Corroborating signals
    1 evidence row
    Vendor claim
    a major-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 10, 2026 09:36 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Retool logo

    Retool

    Degraded / partial issue
    Vendor-reported

    Elevated Latency on Query Execution (Retool Cloud)

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 10m ago · vendor posted 4d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Sage Intacct logo

    Sage Intacct

    Degraded / partial issue
    Vendor-reported

    Banking Service - Partial Outage

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 10m ago · vendor posted 18d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: vendor:status.sage.com

    Independent origins
    1
    Corroborating signals
    1 evidence row
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 7, 2026 16:07 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Scaleway logo

    Scaleway

    Degraded / partial issue
    Vendor-reported

    [Support] Delays in ticket processing

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 10m ago · vendor posted 1d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Shippo logo

    Shippo

    Degraded / partial issue
    Vendor-reported

    Elevated error rate on DPD Germany Tracking

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 3m ago · vendor posted 6h ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: vendor:status.goshippo.com

    Independent origins
    1
    Corroborating signals
    1 evidence row
    Vendor claim
    a major-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 10, 2026 06:55 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Showmax logo

    Showmax

    Degraded / partial issue
    PulseWatch observed

    DNS resolution failures observed by public resolvers.

    Scope: measured endpoint · Affected geography not established

    1 independent measurement origin · checked just now

    View our measurements
    • public-dns-consensus · availability · observed 2m ago

    Vendor confirmation is not required. These findings describe the measured scope; paging requires independent corroboration.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    Evidence strength

    PulseWatch observed

    1 independent origin.

    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.

  • Slack logo

    Slack

    Degraded / partial issue
    Vendor-reported

    Slack: Slack for iOS closing unexpectedly when opening channels

    Affected scope is described in the vendor notice; service-wide impact is not established.

    official status feed · checked 3m ago · vendor posted 21h ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: vendor:status.slack.com

    Independent origins
    1
    Corroborating signals
    1 evidence row
    Vendor claim
    partial
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 9, 2026 15:56 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Snowflake logo

    Snowflake

    Degraded / partial issue
    Vendor-reported

    INC20000150

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 3m ago · vendor posted 1mo ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Spendesk logo

    Spendesk

    Degraded / partial issue
    Vendor-reported

    3DS Authentication – Notifications Not Received on iOS

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 9m ago · vendor posted 3d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Sumsub logo

    Sumsub

    Degraded / partial issue
    Vendor-reported

    Connectivity issues for some users in Vietnam

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 1m ago · vendor posted 7d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Twilio logo

    Twilio

    Degraded / partial issue
    Vendor-reported

    Twilio: SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in New Zealand

    Affected scope is described in the vendor notice; service-wide impact is not established.

    official status feed · checked 3m ago · vendor posted 9h ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: vendor:status.twilio.com

    Independent origins
    1
    Corroborating signals
    1 evidence row
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 10, 2026 08:31 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • UpCloud logo

    UpCloud

    Degraded / partial issue
    Vendor-reported

    [SG-SIN1] Managed Object Storage Issue

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 1h ago · vendor posted 4d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • WatchGuard Cloud logo

    WatchGuard Cloud

    Degraded / partial issue
    Vendor-reported

    2026-10-09 - GLOBAL - Panda System Management operational issues

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 1h ago · vendor posted 1d ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: status.watchguard.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 9, 2026 08:45 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Wiz logo

    Wiz

    Degraded / partial issue
    Vendor-reported

    AWS me-central-1 Service Disruption

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 1h ago · vendor posted 7mo ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Xendit logo

    Xendit

    Degraded / partial issue
    Vendor-reported

    Over-The-Counter ECPAY_LOAN Philippines Disruption

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 1h ago · vendor posted 4h ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Detected byVendor statement

    Source: status.xendit.co

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 9, 2026 07:20 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

  • Zulip logo

    Zulip

    Degraded / partial issue
    Vendor-reported

    Partially Degraded Service

    Affected scope is described in the vendor notice; service-wide impact is not established.

    vendor status API · checked 1h ago

    This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.

    Observed health

    Unknown

    No samples qualify for a combined success and latency score.

    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.

33 other services have open records awaiting fresh corroboration (28 after grouping services that show the same vendor notice). Those records alone do not establish a current issue.

Open records without current evidence (4)

These services have an open incident record but no current vendor notice, corroborated evidence or PulseWatch finding. A record alone does not establish a current issue.

  • GitHub logo

    GitHub

    Record opened 2d ago
    Detected byVendor statement

    Source: vendor:githubstatus.com

    Independent origins
    1
    Corroborating signals
    1 evidence row
    Vendor claim
    a critical-impact incident
    Our evidence-based assessment
    moderategraded from this incident’s evidence · Oct 7, 2026 15:47 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

  • FOSSA logo

    FOSSA

    Record opened 3d ago
    Detected byVendor statement

    Source: vendor:status.fossa.com

    Independent origins
    1
    Corroborating signals
    1 evidence row
    Vendor claim
    a partial outage
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 6, 2026 21:25 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

  • Airwallex logo

    Airwallex

    Record opened 7d ago
    Detected byVendor statement

    Source: status.airwallex.com

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a major-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Oct 3, 2026 11:50 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.

  • Snyk logo

    Snyk

    Record opened 11d ago
    Detected byVendor statement

    Source: status.snyk.io

    Independent origins
    0
    Corroborating signals
    None in current evidence
    Vendor claim
    a minor-impact incident
    Our evidence-based assessment
    minorgraded from this incident’s evidence · Sep 29, 2026 12:56 UTC

    The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.