by HonkWatch

Is Pitneybowes down in São Tomé and Príncipe?

Pitneybowes has problems

São Tomé and Príncipe No reports in the last hour checked 5 min ago
Partial outage reported by Pitneybowes 1 of 134 parts affected: Carriers / FedEX. Going on for 28 min. Updated 7 Nov, 06:23 UTC, 5 min ago · Official status page
Report a problemFollow community reports
Change country

Reports from people in São Tomé and Príncipe

Last 24 hours · São Tomé and Príncipe · times in UTC

0 reports

No community reports in the last 24 hours from São Tomé and Príncipe. Having trouble? Add your report.

024 12:0018:0000:0006:00

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Report totals as of 7 Nov, 06:28 UTC

Report a problem with Pitneybowes

Having trouble? Tap what isn't working. No account needed.

What isn't working?

Anonymous · one report per service per hour. This adds your experience to the chart, without contacting the provider or subscribing you to alerts.

Compare worldwide reports · Other services in São Tomé and Príncipe

Monitor the provider status with HonkWatch

Get monitoring alerts for Pitneybowes

HonkWatch watches the Pitneybowes status page for you and alerts you by email, Slack, Discord or Telegram when it reports a problem.

Free account required. Pitneybowes is selected on the next page. Review the monitor and choose where alerts go. Community reports do not trigger these monitoring alerts.

Start free Log in

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for São Tomé and Príncipe. The report chart above is filtered to São Tomé and Príncipe.

Our own checks of pitneybowes.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Jakarta: loaded in 1277 ms St. Louis: loaded in 560 ms Toronto: loaded in 284 ms Atlanta: loaded in 263 ms Los Angeles: loaded in 707 ms Dallas: loaded in 434 ms Melbourne: loaded in 1190 ms Singapore: loaded in 1552 ms Amsterdam: loaded in 565 ms Cape Town: loaded in 1460 ms Sydney: loaded in 1427 ms Tokyo: loaded in 1430 ms Delhi: loaded in 1216 ms Hong Kong: loaded in 2553 ms Port Louis: loaded in 2386 ms Mumbai: loaded in 1426 ms Osaka: loaded in 963 ms Querétaro: loaded in 486 ms Portsmouth: loaded in 629 ms Warsaw: loaded in 691 ms Madrid: loaded in 683 ms London: loaded in 462 ms Tel Aviv: loaded in 1108 ms Doha: loaded in 1800 ms Hamina: loaded in 1321 ms Seattle: loaded in 744 ms Lauterbourg: loaded in 623 ms Bangalore: loaded in 1649 ms New Jersey: loaded in 843 ms Seoul: loaded in 2013 ms Frankfurt: loaded in 565 ms Johannesburg: loaded in 1414 ms New York: loaded in 204 ms São Paulo: loaded in 685 ms Santiago: loaded in 1517 ms
  • JakartaReachable1277 ms, 1 min ago
  • St. LouisReachable560 ms, 2 min ago
  • TorontoReachable284 ms, 2 min ago
  • AtlantaReachable263 ms, 2 min ago
  • Los AngelesReachable707 ms, 2 min ago
  • DallasReachable434 ms, 2 min ago
  • MelbourneReachable1190 ms, 2 min ago
  • SingaporeReachable1552 ms, 2 min ago
  • AmsterdamReachable565 ms, 2 min ago
  • Cape TownReachable1460 ms, 2 min ago
  • SydneyReachable1427 ms, 2 min ago
  • TokyoReachable1430 ms, 2 min ago
  • DelhiReachable1216 ms, 2 min ago
  • Hong KongReachable2553 ms, 2 min ago
  • Port LouisReachable2386 ms, 2 min ago
  • MumbaiReachable1426 ms, 2 min ago
  • OsakaReachable963 ms, 2 min ago
  • QuerétaroReachable486 ms, 2 min ago
  • PortsmouthReachable629 ms, 2 min ago
  • WarsawReachable691 ms, 2 min ago
  • MadridReachable683 ms, 3 min ago
  • LondonReachable462 ms, 3 min ago
  • Tel AvivReachable1108 ms, 3 min ago
  • DohaReachable1800 ms, 3 min ago
  • HaminaReachable1321 ms, 3 min ago
  • SeattleReachable744 ms, 3 min ago
  • LauterbourgReachable623 ms, 3 min ago
  • BangaloreReachable1649 ms, 3 min ago
  • New JerseyReachable843 ms, 3 min ago
  • SeoulReachable2013 ms, 3 min ago
  • FrankfurtReachable565 ms, 3 min ago
  • JohannesburgReachable1414 ms, 3 min ago
  • New YorkReachable204 ms, 3 min ago
  • São PauloReachable685 ms, 3 min ago
  • SantiagoReachable1517 ms, 3 min ago

This is separate from the status page: we request pitneybowes.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Pitneybowes

Pitney Bowes

Carriers

  • FedEXPartial outage

133 other parts are working.

Incidents and maintenance

Open incidents

  • FedEx Service Disruption Observed for RateShipment. (investigating) Since 7 Nov, 05:53 UTC. Affects FedEX · Details

Maintenance

  • USPS Tracking Scheduled Maintenance (planned) 9 Nov, 01:00 UTC to 9 Nov, 09:00 UTC. Affects Tracking · Details
  • USPS APIs Maintenance - 08 November 2026 (planned) 9 Nov, 01:00 UTC to 9 Nov, 07:00 UTC. Affects Tracking · Details
  • USPS APIs Maintenance - 12 November 2026 (planned) 13 Nov, 01:00 UTC to 13 Nov, 05:00 UTC. Affects Create Label, Create Manifest, Get Rates, Tracking · Details
  • USPS APIs Maintenance - 14 November 2026 (planned) 15 Nov, 04:00 UTC to 15 Nov, 09:00 UTC. Affects Create Label · Details
Outage history

Last 9030 days

97.67% of the time without a reported outage, since 3 Nov

Of the last 90 days, 1 had a partial or major outage, 1 had maintenance only and 85 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of pitneybowes.com that failed (9,640 checks). Shaded: when Pitneybowes's status page reported a problem. Community reports appear separately above, alongside our checks and provider updates.

0%5%10% 12:0018:0000:0006:00 0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed1% of 108 checks failed0% of 105 checks failed0% of 105 checks failed0% of 104 checks failed0% of 104 checks failed0% of 92 checks failed0% of 99 checks failed0% of 102 checks failed0% of 99 checks failed0% of 107 checks failed0% of 88 checks failed0% of 77 checks failed0% of 102 checks failed0% of 100 checks failed0% of 102 checks failed0% of 103 checks failed0% of 98 checks failed0% of 75 checks failed0% of 88 checks failed0% of 93 checks failed0% of 102 checks failed0% of 89 checks failed0% of 98 checks failed0% of 102 checks failed0% of 108 checks failed0% of 94 checks failed0% of 79 checks failed0% of 83 checks failed0% of 108 checks failed0% of 86 checks failed0% of 88 checks failed0% of 80 checks failed0% of 84 checks failed0% of 87 checks failed0% of 108 checks failed0% of 89 checks failed0% of 105 checks failed0% of 103 checks failed0% of 86 checks failed0% of 103 checks failed0% of 105 checks failed0% of 101 checks failed0% of 81 checks failed1% of 112 checks failed0% of 112 checks failed0% of 82 checks failed0% of 88 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 96 checks failed0% of 105 checks failed0% of 105 checks failed0% of 95 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed

Recent problems

7 Nov, 06:00 UTCPartial outagegoing on, 28 min1 of 134 parts affected: Carriers / FedEX
7 Nov, 05:13 UTCPartial outage39 min1 of 134 parts affected: Carriers / FedEX
7 Nov, 03:55 UTCPartial outage1 h 3 min1 of 134 parts affected: Carriers / FedEX
What can I try?

Having trouble with Pitneybowes?

  1. Compare reports from São Tomé and Príncipe and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is Pitneybowes down, or is it just me?

Pitneybowes itself reports a problem right now, so it is probably not just you.

How do we know?

We read the official Pitneybowes status page and load pitneybowes.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 7.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

More in Business software

See the live outage feed for São Tomé and Príncipe · Find another service