Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Outage in Tinybird

Connectivity issues affecting traffic in AWS us-east

Resolved Minor
May 08, 2026 - Started 1 day ago - Lasted about 6 hours

Incident Report

Summary AI Generated

Tinybird experienced connectivity issues in the AWS us-east region for 5.8 hours, causing increased latency and occasional delays for a subset of user requests. The problem was traced to network-level packet loss between the load balancer infrastructure and the public internet. The team investigated infrastructure and network layers while working on mitigation options to reduce impact during the incident.

We're currently investigating a connectivity issue affecting a subset of traffic in region AWS us-east. Some requests may experience increased latency or occasional delays. Our initial analysis indicates this is caused by network-level packet loss on the path between our load balancer infrastructure and the public internet. At this stage, we do not believe this is related to application code, recent changes, or backend service saturation. We're continuing to investigate at the infrastructure and network layer, including host-level networking, NIC behavior, and potential AWS network/AZ conditions. We're also working on mitigation options to reduce the impact while we identify the root cause. We'll share updates as soon as we have more information.

Trusted by 1,000+ teams

Never miss outages in third-party dependencies

Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.

IsDown status aggregator dashboard
Latest Updates ( sorted recent to last )
INVESTIGATING 1 day ago - at 05/08/2026 10:30AM

We're currently investigating a connectivity issue affecting a subset of traffic in region AWS us-east. Some requests may experience increased latency or occasional delays.

Our initial analysis indicates this is caused by network-level packet loss on the path between our load balancer infrastructure and the public internet. At this stage, we do not believe this is related to application code, recent changes, or backend service saturation.

We're continuing to investigate at the infrastructure and network layer, including host-level networking, NIC behavior, and potential AWS network/AZ conditions. We're also working on mitigation options to reduce the impact while we identify the root cause.

We'll share updates as soon as we have more information.

Never miss outages in third-party dependencies

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6320 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook