Periskope logo

Is Periskope Down?

CommunicationLive status, outages, and incident history

No. Periskope is up right now.

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

OperationalChecked 2m agoLive · every 60s

Know the moment Periskope breaks

Periskope is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

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

Official Periskope status page
How we know: the official Periskope status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Periskope Status Summary

As of 17:13 UTC on 14 November 2026, Periskope is operational. PulsAPI checked Periskope's official status page and found 6 of 6 components operational, with no active incidents. The latest incident, "Services are temporarily degraded.", was on Nov 13, 2026 and lasted 5 min.

Cite as: PulsAPI, “Periskope status”, checked 14 November 2026, 17:13 UTC. https://www.pulsapi.com/services/periskope

Periskope Component Status

The main Periskope systems on this page. All 6 are operational right now.

6operational
Analytics
Operational
APIs
Operational
Automation Rules
Operational

3 more components tracked

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

Also tracking Chats & Tickets, Periskope Console, Webhooks.

See all of them free

Component statuses may change independently during partial outages.

Recent Periskope Outages & Incidents

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

Services are temporarily degraded.Resolved Nov 13, 2026 · 5 minResolved
Services are temporarily degraded.Resolved Oct 31, 2026 · 0 minResolved
We are experiencing delays in some phonesResolved Sep 24, 2026 · 2h 35mResolved

Periskope Uptime History

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

Uptime history3 days observed
Nov 12100.00% average · 1 day with incidentsNov 14

Live Periskope Outage Reports

Problems reported by engineers using Periskope. 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

No Periskope problems reported yet.

Something wrong with Periskope on your end?

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

About Periskope

Periskope's status page at status.periskope.app lists 6 components, such as APIs, Analytics and Automation Rules. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Periskope's side or yours.

Periskope Status FAQ

Is Periskope down right now?

The verdict at the top of this page comes from the latest poll of the official Periskope status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Periskope 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 Periskope recovers.

How do I check Periskope uptime history?

PulsAPI tracks Periskope uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Periskope changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Periskope outages?

PulsAPI reads the official Periskope status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Periskope components?

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

Can I get alerts when Periskope goes down?

Yes. Create a free account and subscribe to Periskope: 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 Periskope 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 Periskope problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Periskope?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Periskope 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 Periskope with the rest of your stack

4372+ 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