Vendor reports: degradedResolved · vendor status “resolved”Vendor incident feed · inferred

Gap in Collection Metrics

Reported by Monte Carlo · Data & Analytics · source last read just now

Official source (opens in a new tab)
Vendor posted
Jul 31, 2025, 07:00 UTC
When the vendor's feed dated it
Resolved
Jul 31, 2025, 07:00 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 02:12 UTC
Statuswall's clock
Duration
Not available
This source does not publish reliable durations

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Monte Carlo reports degraded: "Gap in Collection Metrics".[E1, E2]
  • The vendor marked it resolved at 2025-07-31 07:00 UTC.[E3, E7]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-11-11 02:12 UTC · summary s1, evidence b32eb2a3425a5c43

Evidence (8)
  1. E1Monte Carlo reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Gap in Collection Metrics". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor posted it: 2025-07-31 07:00 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2025-07-31 07:00 UTC. (vendor) source (opens in a new tab)
  8. E8First seen by Statuswall: 2026-11-11 02:12 UTC. (Statuswall)

Affected scope

Not stated by the vendor

Components: not stated by the vendor

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Monte Carlo is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jul 31, 2025, 07:00 UTCVendor posted this incidentVendor time
  2. Jul 31, 2025, 07:00 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 02:12 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall