Visp logo

Is Visp Down?

SaaSLive status, outages, and incident history

No. Visp is up right now.

Every monitored Visp 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 Visp breaks

Visp 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 Visp status page
How we know: the official Visp status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Visp Status Summary

As of 14:12 UTC on 14 November 2026, Visp is operational. PulsAPI checked Visp's official status page and found 17 of 17 components operational, with no active incidents. The latest incident, "Application Error After Recent Release : "We're sorry, but something went wrong."", was on Sep 2, 2026 and lasted 22h 36m.

Cite as: PulsAPI, “Visp status”, checked 14 November 2026, 14:12 UTC. https://www.pulsapi.com/services/visp

Visp Component Status

The main Visp systems on this page. All 17 are operational right now.

17operational
API
Operational
RADIUS
Operational
Third Party » Authorize.net
Operational

14 more components tracked

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

Also tracking Third Party » Elavon, Third Party » Email Service - OpenSRS, Third Party » Hosting Service - Hostopia, Third Party » IPpay, Third Party » Oriental Bank, Third Party » PaydUp.net, Third Party » Payment Express, Third Party » Paypal, Third Party » PlugNPay, Third Party » ProPay, Third Party » Stripe, UBO, and 2 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Visp Outages & Incidents

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

Application Error After Recent Release : "We're sorry, but something went wrong."Resolved Sep 2, 2026 · 22h 36mResolved

Fixed the issue where some users were seeing an outdated version of the application after a release. Browsers will now automatically load the latest version, eliminating the need for a manual cache refresh in most cases. If you need assistance , contact the Client Success Team --- [2026-09-03T11:14:01.035Z] (identified) We are continuing to work on a fix for this issue. --- [2026-09-02T12:38:31.731Z] (identified) Following a recent release, some users may encounter the message: "We're sorry, but something went wrong." This can occur when opening customer accounts or navigating to other areas of the application. The issue is typically caused by the browser loading an older cached version of the application while newer files have already been deployed. Required Action: Perform a hard refresh by pressing Ctrl + F5 (Windows) or Cmd + Shift + R (Mac). If the issue continues, clear your browser cache and reload the application. This will ensure your browser downloads the latest application build and resolves the mismatch between cached and updated files. If you continue to experience issues after performing these steps, please contact the VISP Client Success Team for assistance. We apologize for the inconvenience and appreciate your patience.

Error When Attempting to Load or View StatementsResolved Aug 26, 2026 · 14h 38mResolved

This issue has been resolved. Statement viewing and loading are now functioning normally, and users should no longer encounter errors when accessing statements. Thank you for your patience while we worked to restore service. --- [2026-08-26T14:34:00.919Z] (investigating) We are investigating an issue causing a "Sorry, something went wrong" error when loading or viewing statements. The issue has been confirmed across multiple ISP instances, and our technical team is actively working on a resolution. We will provide updates as more information becomes available. Thank you for your patience.

Visp Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Visp 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% averageNov 14

Live Visp Outage Reports

Problems reported by engineers using Visp. 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 Visp problems reported yet.

Something wrong with Visp on your end?

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

About Visp

Visp's status page at status.visp.net lists 17 components, such as API, RADIUS and Authorize.net. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Visp's side or yours.

Visp Status FAQ

Is Visp down right now?

The verdict at the top of this page comes from the latest poll of the official Visp 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 Visp 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 Visp recovers.

How do I check Visp uptime history?

PulsAPI tracks Visp 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 Visp changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Visp outages?

PulsAPI reads the official Visp 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 Visp components?

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

Can I get alerts when Visp goes down?

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

Is there a free way to monitor Visp?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Visp 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 Visp 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