ByteDance status

Q: Is ByteDance down right now?

ByteDance does not publish a machine-readable status feed. This page shows the success rate LLM Gateway measured on real ByteDance traffic over the last 24 hours and 90 days.

Q: How is ByteDance uptime measured?

Uptime is the share of requests to ByteDance through LLM Gateway that completed without a provider or gateway error. Invalid requests (4xx caused by the request) and traffic on customers' own provider keys are excluded.

Q: What happens to my requests when ByteDance has an outage?

LLM Gateway retries failed requests on another healthy provider serving the same model and routes new traffic away from degraded providers. 6 of the 24 ByteDance models on LLM Gateway can fail over this way.

Q: How often does this page update?

Every five minutes. Measured uptime comes from LLM Gateway's hourly traffic rollups; the official status and incidents come from the provider's status page.

Is ByteDance down? Live official status, incidents, and the uptime LLM Gateway measured on real ByteDance traffic.

No official feed

Measured uptime

Success rate of ByteDance requests through LLM Gateway, by UTC day.

Last 24 hours

—

Not enough traffic

Last 90 days

99.05%

71,552 requests

Aug 11: Not enough traffic to measure
Aug 12: Not enough traffic to measure
Aug 13: Not enough traffic to measure
Aug 14: Not enough traffic to measure
Aug 15: Not enough traffic to measure
Aug 16: Not enough traffic to measure
Aug 17: Not enough traffic to measure
Aug 18: Not enough traffic to measure
Aug 19: Not enough traffic to measure
Aug 20: Not enough traffic to measure
Aug 21: Not enough traffic to measure
Aug 22: Not enough traffic to measure
Aug 23: Not enough traffic to measure
Aug 24: Not enough traffic to measure
Aug 25: Not enough traffic to measure
Aug 26: Not enough traffic to measure
Aug 27: 99.07% uptime over 108 requests
Aug 28: 95.38% uptime over 390 requests
Aug 29: 96.80% uptime over 219 requests
Aug 30: 98.15% uptime over 486 requests
Aug 31: 98.28% uptime over 639 requests
Sep 1: 96.40% uptime over 556 requests
Sep 2: 97.29% uptime over 517 requests
Sep 3: 99.19% uptime over 614 requests
Sep 4: 95.91% uptime over 416 requests
Sep 5: 99.54% uptime over 219 requests
Sep 6: 100% uptime over 139 requests
Sep 7: 97.97% uptime over 541 requests
Sep 8: 99.29% uptime over 705 requests
Sep 9: 99.58% uptime over 1,199 requests
Sep 10: 98.26% uptime over 459 requests
Sep 11: 98.89% uptime over 542 requests
Sep 12: 100% uptime over 342 requests
Sep 13: 100% uptime over 283 requests
Sep 14: Not enough traffic to measure
Sep 15: 100% uptime over 170 requests
Sep 16: Not enough traffic to measure
Sep 17: 98.47% uptime over 131 requests
Sep 18: Not enough traffic to measure
Sep 19: 96.43% uptime over 476 requests
Sep 20: 98.04% uptime over 408 requests
Sep 21: 100% uptime over 282 requests
Sep 22: 95.63% uptime over 710 requests
Sep 23: 98.91% uptime over 275 requests
Sep 24: 99.74% uptime over 772 requests
Sep 25: 99.86% uptime over 715 requests
Sep 26: 99.77% uptime over 1,294 requests
Sep 27: 99.90% uptime over 1,960 requests
Sep 28: 99.76% uptime over 5,500 requests
Sep 29: 98.52% uptime over 5,412 requests
Sep 30: 98.21% uptime over 4,922 requests
Oct 1: 100% uptime over 953 requests
Oct 2: 98.95% uptime over 1,812 requests
Oct 3: 96.86% uptime over 3,657 requests
Oct 4: 100% uptime over 1,102 requests
Oct 5: 99.44% uptime over 2,832 requests
Oct 6: 98.83% uptime over 2,311 requests
Oct 7: 99.84% uptime over 3,769 requests
Oct 8: 99.34% uptime over 4,090 requests
Oct 9: 99.77% uptime over 5,310 requests
Oct 10: 99.55% uptime over 2,233 requests
Oct 11: 100% uptime over 1,046 requests
Oct 12: 100% uptime over 627 requests
Oct 13: 100% uptime over 152 requests
Oct 14: 98.78% uptime over 246 requests
Oct 15: 100% uptime over 122 requests
Oct 16: Not enough traffic to measure
Oct 17: Not enough traffic to measure
Oct 18: 100% uptime over 112 requests
Oct 19: 100% uptime over 1,524 requests
Oct 20: 98.81% uptime over 1,178 requests
Oct 21: 100% uptime over 237 requests
Oct 22: 100% uptime over 786 requests
Oct 23: 97.20% uptime over 214 requests
Oct 24: Not enough traffic to measure
Oct 25: Not enough traffic to measure
Oct 26: 100% uptime over 1,072 requests
Oct 27: 100% uptime over 714 requests
Oct 28: 99.56% uptime over 1,124 requests
Oct 29: 100% uptime over 289 requests
Oct 30: 97.21% uptime over 287 requests
Oct 31: Not enough traffic to measure
Nov 1: 100% uptime over 231 requests
Nov 2: 99.49% uptime over 195 requests
Nov 3: 98.09% uptime over 471 requests
Nov 4: 100% uptime over 191 requests
Nov 5: Not enough traffic to measure
Nov 6: 100% uptime over 453 requests
Nov 7: 98.66% uptime over 149 requests
Nov 8: 100% uptime over 112 requests

30 days ago90 days agoToday

≥ 99.5%
≥ 98%
≥ 95%
≥ 90%
< 90%
No data
Official incident

Automatic failover

When ByteDance fails or slows down, LLM Gateway retries the request on another healthy provider serving the same model, with no change to your code. 6 of 24 ByteDance models can fail over.

ByteDance models and pricing Official status page

Frequently asked questions

Is ByteDance down right now?

ByteDance does not publish a machine-readable status feed. This page shows the success rate LLM Gateway measured on real ByteDance traffic over the last 24 hours and 90 days.

How is ByteDance uptime measured?

Uptime is the share of requests to ByteDance through LLM Gateway that completed without a provider or gateway error. Invalid requests (4xx caused by the request) and traffic on customers' own provider keys are excluded.

What happens to my requests when ByteDance has an outage?

LLM Gateway retries failed requests on another healthy provider serving the same model and routes new traffic away from degraded providers. 6 of the 24 ByteDance models on LLM Gateway can fail over this way.

How often does this page update?

Every five minutes. Measured uptime comes from LLM Gateway's hourly traffic rollups; the official status and incidents come from the provider's status page.