Codex666

codex666.zeabur.app

LMSpeed tracks Codex666 API pricing, model coverage, speed tests, and uptime signals for codex666.zeabur.app.

Codex666 provides API conversion and unified access to multiple AI models through OpenAI-compatible endpoints.

Codex666 offers 2 LLM API models.

Speed benchmark average: 53 tok/s.

Avg Speed52.56 tok/s

Latency2.71 s

Updated6/8/2026

Created At4/3/2026

Unhealthy

Last checked 6/9/2026, 5:45:16 AM

Day

Recent availability

Week

Recent availability

Month

7.2%

Recent availability

Latency

—

Health Check

1000History (1000 pts)

PastNow

Time	Status	Hourly uptime	Latency
2026-06-09	0/15	0%	—
2026-06-08	0/57	0%	—
2026-06-07	0/57	0%	—
2026-06-06	0/54	0%	—
2026-06-05	0/54	0%	—
2026-06-04	0/52	0%	—
2026-06-03	0/54	0%	—
2026-06-02	0/60	0%	—
2026-06-01	0/56	0%	—
2026-05-31	0/59	0%	—
2026-05-30	0/60	0%	—
2026-05-29	0/59	0%	—
2026-05-28	0/55	0%	—
2026-05-27	0/60	0%	—
2026-05-26	0/61	0%	—
2026-05-25	0/58	0%	—
2026-05-24	3/60	5%	726ms
2026-05-23	56/56	100%	642ms
2026-05-22	13/13	100%	577ms

Time	Status Code	Latency	Error
6/9/2026, 5:45:16 AM	HTTP 404	—	HTTP 404
6/9/2026, 5:16:24 AM	HTTP 404	—	HTTP 404
6/9/2026, 4:46:20 AM	HTTP 404	—	HTTP 404
6/9/2026, 4:16:10 AM	HTTP 404	—	HTTP 404
6/9/2026, 3:54:52 AM	HTTP 404	—	HTTP 404
6/9/2026, 3:34:59 AM	HTTP 404	—	HTTP 404
6/9/2026, 3:05:34 AM	HTTP 404	—	HTTP 404
6/9/2026, 2:36:22 AM	HTTP 404	—	HTTP 404
6/9/2026, 2:05:39 AM	HTTP 404	—	HTTP 404
6/9/2026, 1:44:58 AM	HTTP 404	—	HTTP 404
6/9/2026, 1:25:22 AM	HTTP 404	—	HTTP 404
6/9/2026, 1:04:10 AM	HTTP 404	—	HTTP 404
6/9/2026, 12:44:19 AM	HTTP 404	—	HTTP 404
6/9/2026, 12:24:02 AM	HTTP 404	—	HTTP 404
6/9/2026, 12:03:38 AM	HTTP 404	—	HTTP 404
6/8/2026, 11:43:50 PM	HTTP 404	—	HTTP 404
6/8/2026, 11:24:09 PM	HTTP 404	—	HTTP 404
6/8/2026, 11:03:03 PM	HTTP 404	—	HTTP 404
6/8/2026, 10:43:09 PM	HTTP 404	—	HTTP 404
6/8/2026, 10:22:59 PM	HTTP 404	—	HTTP 404

Check target: the provider's dedicated health check URL, or its website URL as fallback.
Request method: HTTP GET with automatic redirect following.
Healthy criteria: HTTP status code 200–399 is considered healthy; any other status or network error is unhealthy.
Timeout: each check has a 5-second timeout. If the server does not respond within 5 s, the check is marked as failed.
Frequency: health checks run periodically via an automated cron job for all providers.

Health history

Time	Status	Hourly uptime	Latency
2026-06-09	0/15	0%	—
2026-06-08	0/57	0%	—
2026-06-07	0/57	0%	—
2026-06-06	0/54	0%	—
2026-06-05	0/54	0%	—
2026-06-04	0/52	0%	—
2026-06-03	0/54	0%	—
2026-06-02	0/60	0%	—
2026-06-01	0/56	0%	—
2026-05-31	0/59	0%	—
2026-05-30	0/60	0%	—
2026-05-29	0/59	0%	—
2026-05-28	0/55	0%	—
2026-05-27	0/60	0%	—
2026-05-26	0/61	0%	—
2026-05-25	0/58	0%	—
2026-05-24	3/60	5%	726ms
2026-05-23	56/56	100%	642ms
2026-05-22	13/13	100%	577ms

Recent Incidents

Time	Status Code	Latency	Error
6/9/2026, 5:45:16 AM	HTTP 404	—	HTTP 404
6/9/2026, 5:16:24 AM	HTTP 404	—	HTTP 404
6/9/2026, 4:46:20 AM	HTTP 404	—	HTTP 404
6/9/2026, 4:16:10 AM	HTTP 404	—	HTTP 404
6/9/2026, 3:54:52 AM	HTTP 404	—	HTTP 404
6/9/2026, 3:34:59 AM	HTTP 404	—	HTTP 404
6/9/2026, 3:05:34 AM	HTTP 404	—	HTTP 404
6/9/2026, 2:36:22 AM	HTTP 404	—	HTTP 404
6/9/2026, 2:05:39 AM	HTTP 404	—	HTTP 404
6/9/2026, 1:44:58 AM	HTTP 404	—	HTTP 404
6/9/2026, 1:25:22 AM	HTTP 404	—	HTTP 404
6/9/2026, 1:04:10 AM	HTTP 404	—	HTTP 404
6/9/2026, 12:44:19 AM	HTTP 404	—	HTTP 404
6/9/2026, 12:24:02 AM	HTTP 404	—	HTTP 404
6/9/2026, 12:03:38 AM	HTTP 404	—	HTTP 404
6/8/2026, 11:43:50 PM	HTTP 404	—	HTTP 404
6/8/2026, 11:24:09 PM	HTTP 404	—	HTTP 404
6/8/2026, 11:03:03 PM	HTTP 404	—	HTTP 404
6/8/2026, 10:43:09 PM	HTTP 404	—	HTTP 404
6/8/2026, 10:22:59 PM	HTTP 404	—	HTTP 404

Health Check Rules

Check target: the provider's dedicated health check URL, or its website URL as fallback.
Request method: HTTP GET with automatic redirect following.
Healthy criteria: HTTP status code 200–399 is considered healthy; any other status or network error is unhealthy.
Timeout: each check has a 5-second timeout. If the server does not respond within 5 s, the check is marked as failed.
Frequency: health checks run periodically via an automated cron job for all providers.