Status: Monitoring We've identified the root cause and applied the fix, and latencies are back to normal now Affected components
 <ul>
 <li>API Endpoints (Operational)</li>
<li>Query API (Operational)</li>
 </ul>

Increased latencies in aws-us-west-2

Status: Resolved We've identified the root cause that was slowing down a small percentage of requests and have applied the solution. Affected components
 <ul>
 <li>API Endpoints (Operational)</li>
<li>Events API (Operational)</li>
<li>Query API (Operational)</li>
 </ul>

Connectivity issues affecting traffic in AWS us-east

Status: Resolved We've caught up with ingestion. Affected components
 <ul>
 <li>Events API (Operational)</li>
<li>Kafka (Operational)</li>
<li>S3 Connector (Operational)</li>
 </ul>

Degraded ingestion in gcp-us-east4

Status: Resolved The job queue processing issue has been fully resolved. All pending jobs are being processed and the system is operating normally.

We apologize for the disruption caused and thank you for your patience.

Job Queue Degradation

Status: Resolved The credential rotation has been completed successfully. All services are operating normally and the impact caused by the incident has been resolved.

We appreciate your patience during this time. If you continue to experience any issues, please don't hesitate to reach out. Affected components
 <ul>
 <li>Login (Operational)</li>
<li>Login (Operational)</li>
<li>Login (Operational)</li>
<li>Login (Operational)</li>
<li>Login (Operational)</li>
<li>Login (Operational)</li>
<li>Login (Operational)</li>
<li>Login (Operational)</li>
 </ul>

Several Tinybird services might be affected

Status: Resolved We were impacted by a spike of requests to the v0/events endpoint which bypass our protections in our load balancers causing a saturation of them which impacted on the rest of the requests. 

We have added extra resources to be able to handle any news spikes and we started to work on better protections to avoid any new incident

Load balance unresponsive in GCP US East

Status: Resolved Everything should be working now Affected components
 <ul>
 <li>BI Connector (Operational)</li>
<li>CSV Imports (Operational)</li>
<li>Copy (Operational)</li>
<li>S3 Connector (Operational)</li>
<li>GCS Connector (Operational)</li>
<li>Query API (Operational)</li>
<li>Sinks (Operational)</li>
<li>Events API (Operational)</li>
<li>Kafka (Operational)</li>
<li>API Endpoints (Operational)</li>
 </ul>

Public cluster in GCP us east down

Status: Resolved UI is fully restored and operative Affected components
 <ul>
 <li>Tinybird UI (Operational)</li>
 </ul>

UI is not accessible

Status: Resolved The region is recovered. Affected components
 <ul>
 <li>Kafka (Operational)</li>
<li>Query API (Operational)</li>
<li>Copy (Operational)</li>
<li>S3 Connector (Operational)</li>
<li>GCS Connector (Operational)</li>
<li>Events API (Operational)</li>
<li>API Endpoints (Operational)</li>
<li>CSV Imports (Operational)</li>
<li>Sinks (Operational)</li>
 </ul>

GCP us-east4 region degraded

Status: Resolved All systems back to normal. No remaining lag to process Affected components
 <ul>
 <li>Kafka (Operational)</li>
<li>Kafka (Operational)</li>
 </ul>

Kafka service degradation

Status: Resolved Service is back to normal. Affected components
 <ul>
 <li>GCS Connector (Operational)</li>
<li>API Endpoints (Operational)</li>
<li>Sinks (Operational)</li>
<li>S3 Connector (Operational)</li>
<li>Events API (Operational)</li>
<li>Query API (Operational)</li>
<li>BI Connector (Operational)</li>
<li>CSV Imports (Operational)</li>
<li>Copy (Operational)</li>
<li>Login (Operational)</li>
 </ul>

Service is back to normal in gcp-us-east4

Status: Resolved The incident was caused by a sudden spike of requests. This is now resolved. Affected components
 <ul>
 <li>Query API (Operational)</li>
<li>Sinks (Operational)</li>
<li>GCS Connector (Operational)</li>
<li>Events API (Operational)</li>
<li>BI Connector (Operational)</li>
<li>CSV Imports (Operational)</li>
<li>Copy (Operational)</li>
<li>S3 Connector (Operational)</li>
<li>Login (Operational)</li>
<li>Kafka (Operational)</li>
<li>API Endpoints (Operational)</li>
 </ul>

Degradation in GCP-us-east4

Status: Resolved There was a degradation in the ingestion on gcp-us-east due to some integrity checks, we identified the issue and fixed it. So now we are finishing processing retries and the situation is stable. Affected components
 <ul>
 <li>Events API (Operational)</li>
<li>API Endpoints (Operational)</li>
 </ul>

Degraded performance in gcp-us-east

Status: Resolved Tinybird Dashboard is recovered, the incident in Auth0: https://status.auth0.com/incidents/kknl0nbdzbvx, our identity provider, is now resolved. Affected components
 <ul>
 <li>Tinybird UI (Operational)</li>
 </ul>

Is Tinybird down?

Tinybird status is UP

Lastest published events

Increased latencies in aws-us-west-2

Connectivity issues affecting traffic in AWS us-east

Degraded ingestion in gcp-us-east4

Tinybird Services, Components and Regions

Recent Tinybird events

Increased latencies in aws-us-west-2

Connectivity issues affecting traffic in AWS us-east

Degraded ingestion in gcp-us-east4

Job Queue Degradation

Several Tinybird services might be affected

Load balance unresponsive in GCP US East

Get your FREE account now,
5 monitors included!

Is Tinybird down?

Tinybird status is UP

Lastest published events

Increased latencies in aws-us-west-2

Connectivity issues affecting traffic in AWS us-east

Degraded ingestion in gcp-us-east4

Tinybird Services, Components and Regions

Recent Tinybird events

Increased latencies in aws-us-west-2

Connectivity issues affecting traffic in AWS us-east

Degraded ingestion in gcp-us-east4

Job Queue Degradation

Several Tinybird services might be affected

Load balance unresponsive in GCP US East

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!