LiteLLM logo

Is LiteLLM Down?

AI & Machine LearningLive status, outages, and incident history

No. LiteLLM is up right now.

Every monitored LiteLLM system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · 60s while moving

Know the moment LiteLLM breaks

LiteLLM is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official LiteLLM status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

LiteLLM Component Status

The main LiteLLM systems on this page. All 4 are operational right now.

4operational
ipsos.litellm-prod.ai
Operational
litellm.ai - deployment 1
Operational
litellm.ai - deployment 2
Operational

1 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking litellm.ai - deployment 4.

See all of them free

Component statuses may change independently during partial outages.

Recent LiteLLM Outages & Incidents

Incident history from the official LiteLLM status page, including resolution updates.

No recent incidents reported by the vendor.

LiteLLM Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a LiteLLM incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 899.82% average · 2 days with incidentsSep 25

Live LiteLLM Outage Reports

Problems reported by engineers using LiteLLM. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow
2 most recent reports
Service DownSevereZurich, Switzerlandabout 3 days ago
Service DownMinorUusimaa, Finlandabout 24 days ago

API Error: 503 no healthy upstream. This is a server-side issue, usually temporary — try again in a moment. If it persists, check your inference gateway

Something wrong with LiteLLM on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About LiteLLM

LiteLLM exposes 2 monitored components on its status page at status.litellm.ai — New section among them. Follow LiteLLM downtime, degraded performance and resolved incidents here, with uptime history alongside your other AI and machine learning services.

Over the past 30 days, PulsAPI has measured LiteLLM uptime at 100.00%. Response times, incident history, and SLA tracking for LiteLLM are available on the PulsAPI dashboard.

LiteLLM Status FAQ

Is LiteLLM down right now?

The verdict at the top of this page comes from the latest poll of the official LiteLLM status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if LiteLLM is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until LiteLLM recovers.

How do I check LiteLLM uptime history?

PulsAPI tracks LiteLLM uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever LiteLLM changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect LiteLLM outages?

PulsAPI reads the official LiteLLM status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual LiteLLM components?

Yes. PulsAPI monitors 4 individual LiteLLM components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when LiteLLM goes down?

Yes. Create a free account and subscribe to LiteLLM: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with LiteLLM to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot LiteLLM problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor LiteLLM?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so LiteLLM plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track LiteLLM with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services