Vendor reports: degradedResolved · vendor status “resolved”Official status API

Delayed ingest in EU

Reported by Honeycomb · Observability & Incident · source last read just now

Official source (opens in a new tab)
Vendor start
Jun 10, 2026, 20:58 UTC
Vendor's clock
Resolved
Jun 10, 2026, 22:02 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 h 4 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Honeycomb reports degraded: "Delayed ingest in EU".[E1, E2]
  • The vendor marked it resolved at 2026-06-10 22:02 UTC.[E3, E7]

Affected products and regions

  • Components: api.eu1.honeycomb.io - EU1 Event Ingest, ui.eu1.honeycomb.io - EU1 Querying, ui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting.[E6]

What is unknown

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

Last update in these facts: 2026-06-10 22:02 UTC · summary s1, evidence d5d889db658e11f8

Evidence (7)
  1. E1Honeycomb reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Delayed ingest in EU". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-06-10 20:58 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: api.eu1.honeycomb.io - EU1 Event Ingest, ui.eu1.honeycomb.io - EU1 Querying, ui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-06-10 22:02 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: api.eu1.honeycomb.io - EU1 Event Ingest, ui.eu1.honeycomb.io - EU1 Querying, ui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

Honeycomb 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. Jun 10, 2026, 20:58 UTCVendor-reported startVendor time
  2. Jun 10, 2026, 22:02 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.