globalpayments outages and problems
User reports, last 24 hours
603 reports in total, counted in 15-minute windows
In the last hour, 11 problem reports came in for globalpayments, and at this time of day there are usually almost none. Over the last 24 hours there were 603 reports. Most recent reports were about payments (67%) and login (12%). The last spike in reports was 3 h ago and lasted 1 h 45 min. These are user reports from the US, where most people report globalpayments problems.
- NormalClose to the usual level20 h 30 min · 71 reports
- ElevatedMore than 1.5 times the usual level1 h · 52 reports
- OutageMore than twice the usual level and far above the day's average2 h 30 min · 480 reports
- Usual levelWhat a usual day sees at that timeAlmost none at this time of day
In the past 24 hours, 603 user reports came in for globalpayments. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 89.58% uptime for the day.
The most recent spike big enough to count as an outage was 3 hours ago. The busiest 15-minute window of the day had 82 reports, about 6 hours ago.
-
Outage
Ended 3 h agoLasted 1 h 45 min47peak reports
-
Outage
Ended 5 h agoLasted 2 h 15 min82peak reports
globalpayments in November 2026
- Problem reports in November (since 19 November)
- 603
Monthly report for November 2026
What went wrong
What people said was wrong in recent problem reports for globalpayments.
Share of 49 recent reports that said what was wrong.
Where globalpayments problem reports come from
The map shows where recent problem reports for globalpayments came from in the US. Big cities always send the most, so dots in many places point to a widespread problem, and one area far ahead of the rest can mean a regional one.
- Outage now
- Problems now
- Normal
Map outlines: Natural Earth.
globalpayments problem spikes, last 30 days
Since 19 November, globalpayments had 2 outage spikes. The longest lasted 2 h 15 min, on 20 November.
-
Outage
Fri 20 Nov, 19:29–21:14Lasted 1 h 45 min50peak reports
-
Outage
Fri 20 Nov, 16:44–18:59Lasted 2 h 15 min84peak reports
By country
In the last 2 days, most globalpayments problem reports came from the US (307) and Brazil (0). The latest outage spike was today, in the US.
- The US1 outage day307
- BrazilNo spikes0
- Outage spike
- Elevated reports
- Normal
- No data yet
Each square is one day. It turns red when reports stayed at outage level for half an hour or more, and amber when they stayed above the usual level for an hour or more. The number on the right is the country's total since 19 November 2026, when country history starts. A wider gap marks a Monday. Point at a square, or tap it, for that day's numbers. Days run from midnight to midnight, Central European time.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 19 November 2026. Monthly reports for all services
How to fix globalpayments not working
globalpayments is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach globalpayments.com over your own connection, right now. Nothing is sent to us or stored.
Reload and restart
Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.
Try another connection
Switch between Wi-Fi and mobile data. If it works on one and not the other, the problem is your network, not globalpayments.
Update the app
Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.
Problems at the same time as globalpayments
Since 19 November, all 2 of globalpayments's spikes in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
Most often at the same time
- Microsoft Outlook2 times
- PlayStation Network2 times
- 32Red2 times
- PTCL2 times
- Unibet2 times
- Microsoft 3652 times
How many of globalpayments's spikes overlapped one of theirs.
During the latest spike
globalpayments: Fri 20 Nov, 19:29 to 21:14
- Microsoft Outlook, outage,12 Nov 17:42 to 23:44
- PlayStation Network, outage,17 Nov 09:05 to 23:44
- 32Red, outage,06:29 to 19:44
- PTCL, outage,07:44 to 19:59, 20:49 to 21:06
- Unibet, outage,08:14 to 19:44
- Microsoft 365, outage,11:29 to 23:44
- Yahoo Mail, outage,11:29 to 21:59
- Bank of America, outage,11:29 to 23:44
161 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
globalpayments IP address, servers and network
- IPv4 addresses
- 162.159.140.123
Show all 2
- 172.66.0.121
- IPv6
- Not offered
- Network
- AS13335 · Cloudflare, Inc., registered in the United States
- Served through
- Cloudflare · our check was answered by its Frankfurt (FRA) data centre
- DNS hosted by
- Cloudflare
- HTTPS certificate
- Issued by Sectigo Limited, valid until 30 Jan 2027 (70 days)
- HTTP/3
- Not advertised
- Our check
- Answered in 35 ms (it turned away our automated check, which is common)
Checked from our server in Frankfurt, Germany, 6 h ago, for globalpayments.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 12 places around the world
11 of 12 locations got an answer from globalpayments.com. Fastest from São Paulo (93 ms), slowest from Tokyo (225 ms). Every location connected through Cloudflare, Inc. (AS13335), using 2 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 301 | 148 ms | 172.66.0.121 |
| ViennaAustria | Up · HTTP 301 | 186 ms | 172.66.0.121 |
| MilanItaly | Up · HTTP 301 | 206 ms | 172.66.0.121 |
| ParisFrance | Up · HTTP 301 | 133 ms | 172.66.0.121 |
| AmsterdamNetherlands | Up · HTTP 301 | 109 ms | 162.159.140.123 |
| MadridSpain | Up · HTTP 301 | 122 ms | 172.66.0.121 |
| WarsawPoland | Up · HTTP 301 | 126 ms | 162.159.140.123 |
| DallasUSA | No result | – | – |
| Los AngelesUSA | Up · HTTP 301 | 161 ms | 172.66.0.121 |
| São PauloBrazil | Up · HTTP 301 | 93 ms | 162.159.140.123 |
| SingaporeSingapore | Up · HTTP 301 | 163 ms | 162.159.140.123 |
| TokyoJapan | Up · HTTP 301 | 225 ms | 162.159.140.123 |
Checked with check-host.net from its servers in these cities 6 h ago, for globalpayments.com. Time is how long each server took to load the page.
Contact globalpayments support
Tip: globalpayments doesn't list a public status page that we know of, so its help centre and the report chart on this page are the best places to check.
How we track globalpayments
The status on this page comes from user-submitted problem reports for globalpayments, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for globalpayments, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. globalpayments doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.