by HonkWatch

Is Pitneybowes down in Saint Pierre and Miquelon?

No problems reported with Pitneybowes right now

Saint Pierre and Miquelon No reports in the last hour checked 5 min ago
Pitneybowes reports no current incident. Updated 7 Nov, 07:02 UTC, 5 min ago · Official status page
Report a problemFollow community reports
Change country

Reports from people in Saint Pierre and Miquelon

Last 24 hours · Saint Pierre and Miquelon · times in UTC

0 reports

No community reports in the last 24 hours from Saint Pierre and Miquelon. 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, 07:07 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 Saint Pierre and Miquelon

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 Saint Pierre and Miquelon. The report chart above is filtered to Saint Pierre and Miquelon.

Our own checks of pitneybowes.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Jakarta: loaded in 1535 ms St. Louis: loaded in 439 ms Toronto: loaded in 298 ms Atlanta: loaded in 294 ms Dallas: loaded in 2692 ms Los Angeles: loaded in 693 ms Melbourne: loaded in 1195 ms Lauterbourg: loaded in 747 ms Singapore: loaded in 1476 ms Sydney: loaded in 2638 ms Amsterdam: loaded in 684 ms Cape Town: loaded in 1918 ms Tokyo: loaded in 1106 ms Delhi: loaded in 1314 ms Hong Kong: loaded in 3048 ms Osaka: loaded in 968 ms Port Louis: loaded in 2056 ms Querétaro: loaded in 681 ms Portsmouth: loaded in 591 ms Mumbai: loaded in 2499 ms Madrid: loaded in 636 ms London: loaded in 501 ms Warsaw: loaded in 1080 ms Tel Aviv: loaded in 1024 ms Hamina: loaded in 1161 ms Doha: loaded in 1763 ms Seattle: loaded in 429 ms Bangalore: loaded in 1613 ms New Jersey: loaded in 266 ms Seoul: loaded in 954 ms Frankfurt: loaded in 528 ms Johannesburg: loaded in 1389 ms New York: loaded in 244 ms São Paulo: loaded in 1434 ms Santiago: loaded in 938 ms
  • JakartaReachable1535 ms, just now
  • St. LouisReachable439 ms, just now
  • TorontoReachable298 ms, just now
  • AtlantaReachable294 ms, just now
  • DallasReachable2692 ms, just now
  • Los AngelesReachable693 ms, just now
  • MelbourneReachable1195 ms, just now
  • LauterbourgReachable747 ms, 1 min ago
  • SingaporeReachable1476 ms, 1 min ago
  • SydneyReachable2638 ms, 1 min ago
  • AmsterdamReachable684 ms, 1 min ago
  • Cape TownReachable1918 ms, 1 min ago
  • TokyoReachable1106 ms, 1 min ago
  • DelhiReachable1314 ms, 1 min ago
  • Hong KongReachable3048 ms, 1 min ago
  • OsakaReachable968 ms, 1 min ago
  • Port LouisReachable2056 ms, 1 min ago
  • QuerétaroReachable681 ms, 1 min ago
  • PortsmouthReachable591 ms, 1 min ago
  • MumbaiReachable2499 ms, 2 min ago
  • MadridReachable636 ms, 2 min ago
  • LondonReachable501 ms, 2 min ago
  • WarsawReachable1080 ms, 2 min ago
  • Tel AvivReachable1024 ms, 2 min ago
  • HaminaReachable1161 ms, 2 min ago
  • DohaReachable1763 ms, 2 min ago
  • SeattleReachable429 ms, 2 min ago
  • BangaloreReachable1613 ms, 2 min ago
  • New JerseyReachable266 ms, 2 min ago
  • SeoulReachable954 ms, 2 min ago
  • FrankfurtReachable528 ms, 2 min ago
  • JohannesburgReachable1389 ms, 2 min ago
  • New YorkReachable244 ms, 2 min ago
  • São PauloReachable1434 ms, 2 min ago
  • SantiagoReachable938 ms, 2 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

All 134 listed parts are working.

Incidents and maintenance

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 problem: 7 Nov, 06:00 UTC, partial outage for 31 min (1 of 134 parts affected: Carriers / FedEX).

Last 9030 days

97.64% 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,605 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 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 failed0% of 105 checks failed0% of 105 checks failed0% of 70 checks failed

Recent problems

7 Nov, 06:00 UTCPartial outage31 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 Saint Pierre and Miquelon 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?

The Pitneybowes status page reports no problem and our own checks reach pitneybowes.com. This does not rule out problems with sign-in, payments, an app or a local network. Check the community reports above and report your experience.

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 Saint Pierre and Miquelon · Find another service