Upstash incident: Intermittent DNS Resolution Errors for Upstash Vector in US East (us-east-1)

1. resolvedSep 9, 2026, 12:00 UTC

   Upstash Vector experienced a brief DNS resolution issue in the US East (us-east-1) region lasting approximately 20 minutes. During this period, new DNS resolution attempts may have failed. Existing connections and clients with cached DNS records were not affected. The issue has been resolved, and DNS resolution is operating normally.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Upstash's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Elasticsearch: Replication bug causing slow recoveriesMajor · Sep 1, 2026, 08:16 UTC
• MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Major · Sep 3, 2026, 16:44 UTC
• Miro: Sign-in with username and password is unavailableMajor · Sep 8, 2026, 19:21 UTC
• Confluent Cloud: Connectivity degradation - AWS us-east-1Major · Sep 8, 2026, 20:01 UTC
• OVHcloud: [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notificationMinor · Aug 26, 2026, 15:00 UTC
• Snowflake: INC20000150Minor · Aug 28, 2026, 00:07 UTC
• Telnyx: Intermittent delays for some outbound messagesMinor · Sep 2, 2026, 21:33 UTC
• Confluent Cloud: Service Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1Minor · Sep 8, 2026, 09:17 UTC
• Grafana Cloud: Investigating elevated database load in AWS GermanyMinor · Sep 9, 2026, 11:27 UTC

How often does Upstash have incidents?

Upstash reported 3 incidents in the last 90 days, 1 of them major or critical. See Upstash's uptime and incident history