Is Local API down right now?

Partly. As of 2026-10-10 08:07 UTC, Local API has a partial outage, with an open incident: "Performance Degradation". This page reads the status again every 3 minutes.

Where does this status come from?

From SerpApi's own status page API at https://status.serpapi.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are SerpApi's words. Their page covers more than this page shows; it is narrowed to the parts that concern Local API.

Can I get an alert when Local API goes down?

Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when SerpApi reports an incident that affects Local API and one when it is over. There is also an RSS feed at https://upbutler.com/status/serpapi/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.

How can my agent or app check Local API status?

Fetch https://upbutler.com/status/serpapi/local-api/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"serpapi","component":"local-api"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or SerpApi's?

Add "serpapi" to the dependencies of your UpButler workspace. When one of your monitors fails while SerpApi has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Local API down?

Local API has a partial outage

Right now

Partly. Performance Degradation.

Last checked 3 min ago (2026-10-10 08:07 UTC) from status.serpapi.com · every 180s

For agents

fallback

Use a fallback, next attempt in 300s.

Up right now, same job: Tavily, Exa, Brave Search API, Firecrawl.

GET upbutler.com/status/serpapi/local-api/status.agent.json

MCP: upstream_status {"service":"serpapi","component":"local-api"}

Local API is one of the components SerpApi reports on its status page. Search engine results API.

Part of SerpApi status.

What SerpApi says

Partial outage· 1 open incident

Taken as is from SerpApi's own status page API. Incident titles and component names below are theirs. Narrowed to what concerns Local API.

Open status.serpapi.com

What UpButler measured

There is no keyless endpoint of SerpApi that says anything useful, so UpButler does not probe it. To check your own SerpApi account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at SerpApi for Local API

Performance Degradationidentified · impact major
Since 2026-10-06 15:51 UTC · Search API, Images Light API, News Light API, AI Overview API, Shopping Light API, Videos Light API +6
We've made several adjustments over the past 24 hours and are seeing improved success rates and response times across the affected APIs. However, performance remains degraded, and our engineers are continuing to work toward fully restoring service. Thank you for your continued patience. We'll share further updates as we make progress.

Text written by SerpApi, shown unchanged.

Local API: what SerpApi lists

1 of 1 not operational

Google

Local APIPartial outage

Local API incidents, last 90 days

2026-07-13: no record
2026-07-14: no record
2026-07-15: no record
2026-07-16: no record
2026-07-17: no record
2026-07-18: no record
2026-07-19: no record
2026-07-20: no record
2026-07-21: no record
2026-07-22: no record
2026-07-23: no record
2026-07-24: no record
2026-07-25: no record
2026-07-26: no record
2026-07-27: no record
2026-07-28: no record
2026-07-29: no record
2026-07-30: no record
2026-07-31: no record
2026-08-01: no record
2026-08-02: no record
2026-08-03: no record
2026-08-04: no record
2026-08-05: no record
2026-08-06: no record
2026-08-07: no record
2026-08-08: no record
2026-08-09: no record
2026-08-10: no record
2026-08-11: no record
2026-08-12: no record
2026-08-13: no record
2026-08-14: no record
2026-08-15: no record
2026-08-16: no record
2026-08-17: no record
2026-08-18: no record
2026-08-19: no record
2026-08-20: no record
2026-08-21: no record
2026-08-22: no record
2026-08-23: no record
2026-08-24: no record
2026-08-25: no record
2026-08-26: no record
2026-08-27: no record
2026-08-28: no record
2026-08-29: no record
2026-08-30: no record
2026-08-31: no record
2026-09-01: no record
2026-09-02: no record
2026-09-03: no record
2026-09-04: no record
2026-09-05: no record
2026-09-06: no record
2026-09-07: no record
2026-09-08: no record
2026-09-09: no record
2026-09-10: no record
2026-09-11: no record
2026-09-12: no record
2026-09-13: no record
2026-09-14: no record
2026-09-15: no record
2026-09-16: no record
2026-09-17: major incident
2026-09-18: major incident
2026-09-19: major incident
2026-09-20: major incident
2026-09-21: major incident
2026-09-22: major incident
2026-09-23: major incident
2026-09-24: major incident
2026-09-25: major incident
2026-09-26: major incident
2026-09-27: major incident
2026-09-28: no incident reported
2026-09-29: no incident reported
2026-09-30: no incident reported
2026-10-01: no incident reported
2026-10-02: no incident reported
2026-10-03: no incident reported
2026-10-04: no incident reported
2026-10-05: no incident reported
2026-10-06: major incident
2026-10-07: major incident
2026-10-08: major incident
2026-10-09: major incident
2026-10-10: major incident

2026-07-1316 of 24 days with an incidenttoday

Each bar is a day, coloured by the worst incident SerpApi reported for Local API. It is their incident record, not a measurement of uptime.

Incidents: 1; 1 major or critical
Typical time to resolve: —; median, needs 3 incidents
Nine in ten within: —; 90th percentile
Longest: 9 days; record since 2026-09-17

Started (UTC)	Incident	Impact	Lasted
2026-09-17 22:05	[Google Local API] Performance Degradation	major	9 days

Get alerted when Local API goes down

No account. One email when SerpApi reports an incident that affects Local API, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add SerpApi as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show Local API's current status in a README or an internal wiki. It updates by itself.

[![Local API status](https://upbutler.com/status/serpapi/badge.svg?component=local-api)](https://upbutler.com/status/serpapi/local-api)

Tell your outage from SerpApi's

Declare that your project depends on Local API. When one of your monitors fails while SerpApi has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - service: serpapi
    components: ["Local API"]

Ask before you retry

curl -s https://upbutler.com/status/serpapi/local-api/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "serpapi",
  "component": {
    "slug": "local-api",
    "name": "Local API"
  },
  "verdict": "fallback",
  "status": "partial_outage",
  "reason": "Performance Degradation",
  "retryAfterSec": 300,
  "incident": {
    "title": "Performance Degradation",
    "url": "https://status.serpapi.com/incidents/5pybr6gr3dq4"
  },
  "alternatives": [
    "tavily",
    "exa",
    "brave-search",
    "firecrawl"
  ],
  "probe": null
}

Questions

Is Local API down right now?: Partly. As of 2026-10-10 08:07 UTC, Local API has a partial outage, with an open incident: "Performance Degradation". This page reads the status again every 3 minutes.
Where does this status come from?: From SerpApi's own status page API at https://status.serpapi.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are SerpApi's words. Their page covers more than this page shows; it is narrowed to the parts that concern Local API.
Can I get an alert when Local API goes down?: Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when SerpApi reports an incident that affects Local API and one when it is over. There is also an RSS feed at https://upbutler.com/status/serpapi/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check Local API status?: Fetch https://upbutler.com/status/serpapi/local-api/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"serpapi","component":"local-api"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or SerpApi's?: Add "serpapi" to the dependencies of your UpButler workspace. When one of your monitors fails while SerpApi has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with SerpApi. Status and incident text belong to SerpApi and are read from their public status source; the probe result is UpButler's own measurement.