1. Home
  2. Services
  3. Email, files & productivity
  4. InPost
InPost inpost.pl Live · Operational

Is InPost down right now? Live status and outage tracker

No, InPost is up.

No widespread outage detected. 2 user reports in the last hour is within the normal range.

Reports, last hour
2
Usual at this hour
Almost none
Vs the hour before
−50%

User reports, last 24 hours, one bar per 15 minutes. Dashed line: the usual level. 93 normal · 2 elevated · 1 outage

Not working for you?

Last spike · · Data refreshes every 5 minutes

01 · User reports
2 reports in the last hour

From a public outage-reporting feed, counted in 15-minute windows. The verdict above is based on these.

02 · Our check, Frankfurt
Answered in 143 ms

Our server loaded inpost.pl 33 h ago. Behind Cloudflare.

03 · 12 cities, check-host.net
0 of 12 got an answer

33 h ago.

Last 24 hours

InPost outages and problems

User reports, last 24 hours

201 reports in total, counted in 15-minute windows

In the last hour, 2 problem reports came in for InPost, and at this time of day there are usually almost none. Over the last 24 hours there were 201 reports. Most recent reports were about app (77%) and login (20%). The last spike in reports was 9 h ago and lasted 21 min. These are user reports from Poland, where most people report InPost problems.

In the past 24 hours, 201 user reports came in for InPost. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 98.96% uptime for the day. The most recent spike big enough to count as an outage was 10 hours ago. The busiest 15-minute window of the day had 54 reports, about 10 hours ago.
  • NormalClose to the usual level23 h 15 min · 127 reports
  • ElevatedMore than 1.5 times the usual level30 min · 20 reports
  • OutageMore than twice the usual level and far above the day's average15 min · 54 reports
  • Usual levelWhat a usual day sees at that timeAlmost none at this time of day
Reports, last hour
2
50% on the hour before
Uptime, 24 h
98.96%
15 min of outage
Last outage
10 h ago
Lasted 30 min
Busiest 15 minutes
54
54 reports, 10 h ago
InPost status card: No, InPost is up. User reports over the last 24 hours.
Share this statusThe picture people see when this page is shared: the answer and the last 24 hours of reports.

In the past 24 hours, 201 user reports came in for InPost. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 98.96% uptime for the day.

The most recent spike big enough to count as an outage was 10 hours ago. The busiest 15-minute window of the day had 54 reports, about 10 hours ago.

  • Elevated reports
    Ended 9 h ago
    Lasted 15 min
    10peak reports
  • Outage
    Ended 10 h ago
    Lasted 30 min
    54peak reports
This month

InPost in November 2026

Problem reports in November (since 4 November)
1,379

Monthly report for November 2026

What went wrong

What people said was wrong in recent problem reports for InPost.

  1. App77%
  2. Login20%
  3. Website3%

Share of 35 recent reports that said what was wrong.

World map

Where InPost problem reports come from

The map shows where recent problem reports for InPost came from in Poland. 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
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.

Map outlines: Natural Earth.

Last 30 days

InPost problem spikes, last 30 days

Since 4 November, InPost had 7 outage spikes and 2 periods of elevated reports. The longest lasted 1 h 42 min, on 13 November.

  • Tue 20 Oct: no data
  • Wed 21 Oct: no data
  • Thu 22 Oct: no data
  • Fri 23 Oct: no data
  • Sat 24 Oct: no data
  • Sun 25 Oct: no data
  • Mon 26 Oct: no data
  • Tue 27 Oct: no data
  • Wed 28 Oct: no data
  • Thu 29 Oct: no data
  • Fri 30 Oct: no data
  • Sat 31 Oct: no data
  • Sun 1 Nov: no data
  • Mon 2 Nov: no data
  • Tue 3 Nov: no data
  • Wed 4 Nov: 60 reports
  • Thu 5 Nov: 37 reports
  • Fri 6 Nov: 81 reports
  • Sat 7 Nov: 13 reports
  • Sun 8 Nov: 16 reports
  • Mon 9 Nov: 106 reports (elevated reports that day)
  • Tue 10 Nov: 164 reports (outage spike that day)
  • Wed 11 Nov: 46 reports
  • Thu 12 Nov: 69 reports
  • Fri 13 Nov: 361 reports (outage spike that day)
  • Sat 14 Nov: 92 reports
  • Sun 15 Nov: 34 reports
  • Mon 16 Nov: 99 reports
  • Tue 17 Nov: 200 reports (outage spike that day)
  • Wed 18 Nov: 1 report
  • Elevated reports
    Tue 17 Nov, 15:30–15:51
    Lasted 21 min
    11peak reports
  • Outage
    Tue 17 Nov, 14:36–15:06
    Lasted 30 min
    57peak reports
  • Outage
    Fri 13 Nov, 18:44–19:07
    Lasted 22 min
    12peak reports
  • Outage
    Fri 13 Nov, 16:36–17:36
    Lasted 1 h
    12peak reports
  • Outage
    Fri 13 Nov, 14:01–15:44
    Lasted 1 h 42 min
    16peak reports
  • Outage
    Fri 13 Nov, 12:38–13:19
    Lasted 41 min
    12peak reports
  • Outage
    Fri 13 Nov, 11:31–12:16
    Lasted 45 min
    19peak reports
  • Outage
    Tue 10 Nov, 11:59–12:42
    Lasted 43 min
    27peak reports

1 earlier spike in this period.

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 4 November 2026. Monthly reports for all services

Troubleshooting

How to fix InPost not working

InPost 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 inpost.pl over your own connection, right now. Nothing is sent to us or stored.

  1. Restart InPost Mobile

    Close InPost Mobile from the app switcher, then open it again and refresh the parcels screen. If the parcel list or pickup button was stuck after a network change, this clears the old app session without changing your account.

  2. Check InPost data access

    On iPhone, open Settings > Cellular and turn on Cellular Data, then scroll to InPost and allow it. On Android, open Settings > Network & internet > Internet and switch between Wi-Fi and mobile data; if Data Saver is on, open Settings > Network & internet > Data Saver and turn it off for this test.

  3. Allow pickup permissions

    If the app will not open a Paczkomat locker, check location permission before you try again near the machine. On iPhone, go to Settings > Privacy & Security > Location Services > InPost and choose While Using the App; on Android, go to Settings > Apps > InPost > Permissions > Location and choose Allow only while using the app.

  4. Reinstall InPost Mobile

    Update the app from your phone's app store first, then restart the phone. If it still hangs, uninstall InPost Mobile, install it again, and sign in with the same phone number you used for the shipment so the parcel can appear again.

While it is down

While InPost is down: what to use instead

  • InPost website If the app will not load, try inpost.pl for parcel tracking and basic shipment details.
  • Orlen Paczka Use it for locker or pickup point delivery in Poland when you can choose another carrier at checkout.
  • DPD Pickup It helps when a shop offers courier delivery to a pickup point instead of a parcel locker.
  • Poczta Polska Choose it when you need a post office option for sending or receiving a parcel.
Same time

Problems at the same time as InPost

Since 4 November, all 9 of InPost'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.

A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.

Busiest times

When people report InPost problems

The busiest hour for reports about InPost is 11:00 to 12:00 Central European time, and the busiest day is Friday.

By hour of the day

  • 00:00 to 01:00: 0.27 reports on an average day
  • 01:00 to 02:00: 0.06 reports on an average day
  • 02:00 to 03:00: 0.02 reports on an average day
  • 03:00 to 04:00: 0.02 reports on an average day
  • 04:00 to 05:00: 0.05 reports on an average day
  • 05:00 to 06:00: 0.07 reports on an average day
  • 06:00 to 07:00: 0.15 reports on an average day
  • 07:00 to 08:00: 0.6 reports on an average day
  • 08:00 to 09:00: 1.2 reports on an average day
  • 09:00 to 10:00: 2.3 reports on an average day
  • 10:00 to 11:00: 1.4 reports on an average day
  • 11:00 to 12:00: 2.9 reports on an average day
  • 12:00 to 13:00: 1.6 reports on an average day
  • 13:00 to 14:00: 1.9 reports on an average day
  • 14:00 to 15:00: 2.5 reports on an average day
  • 15:00 to 16:00: 1.5 reports on an average day
  • 16:00 to 17:00: 2 reports on an average day
  • 17:00 to 18:00: 1.7 reports on an average day
  • 18:00 to 19:00: 1.9 reports on an average day
  • 19:00 to 20:00: 1.7 reports on an average day
  • 20:00 to 21:00: 1.2 reports on an average day
  • 21:00 to 22:00: 0.99 reports on an average day
  • 22:00 to 23:00: 0.69 reports on an average day
  • 23:00 to 00:00: 0.42 reports on an average day

By day of the week

  • Monday: 31 reports on an average Monday
  • Tuesday: 39 reports on an average Tuesday
  • Wednesday: 21 reports on an average Wednesday
  • Thursday: 21 reports on an average Thursday
  • Friday: 48 reports on an average Friday
  • Saturday: 18 reports on an average Saturday
  • Sunday: 8.2 reports on an average Sunday

Each bar is the average number of user reports in that hour, or on that day of the week, from 41 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.

About

What happens when InPost goes down

InPost is Poland's parcel locker and courier delivery service, used by shoppers and online stores that send parcels through Paczkomaty and the mobile app. An outage can block parcel tracking, locker pickup, app opening, and label or shipment handling for work orders.

The InPost Mobile app tends to show trouble early: shipments stop loading, and the button to open a locker does nothing. On the website, tracking may stall, and parcel forms may fail to save. At a Paczkomat, you may still collect with a pickup code if the local screen and backend accept it, while app opening can be the part that fails. Problems are often partial or regional, so one locker, one parcel route, courier pickup, or the account area can fail while another city or basic tracking still works.

Servers and network

InPost IP address, servers and network

IPv4 addresses
104.18.41.61
Show all 2
  • 172.64.146.195
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
its own name servers (easypack24.net)
HTTPS certificate
Issued by Google Trust Services, valid until 7 Jan 2027 (50 days)
HTTP/3
Supported
Our check
Answered in 143 ms

Checked from our server in Frankfurt, Germany, 33 h ago, for inpost.pl. 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

All 12 locations got an answer from inpost.pl. Every answer turned the automated check away (HTTP 400), which many sites do with bots; the site itself was up. Fastest from Warsaw (14 ms), slowest from Singapore (1,975 ms). Every location connected through Cloudflare, Inc. (AS13335), using 2 different addresses.

LocationResultTimeAddress reached
FrankfurtGermanyUp · HTTP 40022 ms104.18.41.61
ViennaAustriaUp · HTTP 40016 ms172.64.146.195
MilanItalyUp · HTTP 40019 ms104.18.41.61
ParisFranceUp · HTTP 40047 ms104.18.41.61
AmsterdamNetherlandsUp · HTTP 400120 ms172.64.146.195
MadridSpainUp · HTTP 40069 ms104.18.41.61
WarsawPolandUp · HTTP 40014 ms172.64.146.195
DallasUSAUp · HTTP 400143 ms172.64.146.195
Los AngelesUSAUp · HTTP 400297 ms172.64.146.195
São PauloBrazilUp · HTTP 400171 ms104.18.41.61
SingaporeSingaporeUp · HTTP 4001,975 ms104.18.41.61
TokyoJapanUp · HTTP 400247 ms104.18.41.61

Checked with check-host.net from its servers in these cities 33 h ago, for inpost.pl. Time is how long each server took to load the page.

Questions

InPost FAQ

Is InPost down right now?

The status at the top of this page shows whether user problem reports are above their usual level, counted in 15-minute windows over the last 24 hours. Those reports go to a public outage-reporting service, and this page only reflects that signal. If the graph looks normal, try the app and inpost.pl on mobile data and Wi-Fi, restart the app, and check whether tracking works on another device; if only one phone or connection fails, the issue is probably local.

Why can't the InPost Mobile app open my Paczkomat locker?

Remote opening needs the parcel to be assigned to your phone number in the app, and the phone needs a working data connection near the locker. If the button spins or the locker does not react, switch between Wi-Fi and mobile data, then use the pickup code or QR code from the message as a fallback. When the machine still will not open, use the help option shown at the locker.

Why does parcel tracking show no update after it was placed in a Paczkomat?

Tracking can lag after a sender drops a parcel off, especially before the first depot scan. Check the shipment number for typos, then compare the app with tracking on inpost.pl. If both show the same old step for a long time, the sender may need to confirm handover or ask for the parcel to be checked.

Why am I not getting the SMS or push notification with my pickup code?

The code goes to the phone number tied to the shipment, so one wrong digit on the order can block it. Open the app, check the parcel list under the same number, and look in muted or blocked SMS threads. If the parcel is visible in the app, use its QR code or remote opening instead of waiting for another text.

Why does payment fail when I try to send a parcel?

Payment problems can come from the bank, the card confirmation step, or a stuck app session. Close the payment page and try again, then use another method if the checkout offers one. Do not repeat paid attempts in a hurry; first check your bank app for a charge or reservation.
Official channels

Contact InPost support

Tip: InPost 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.

For your site

Put the InPost status on your site

Paste one of these into a web page, a blog post or a README: a small badge, or a card with the chart. Both show the same status as this page, based on user problem reports, and link back here.

InPost status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/inpost/"><img src="https://isitdownrightnow.app/badge/inpost.svg" alt="InPost status" height="20"></a>
Markdown, for README files
[![InPost status](https://isitdownrightnow.app/badge/inpost.svg)](https://isitdownrightnow.app/services/inpost/)

A live card with the chart

The status, reports in the last hour and the last 24 hours, updated every 5 minutes. Use the frame, or the image where frames are not allowed, such as newsletters.

Frame
<iframe src="https://isitdownrightnow.app/embed/inpost/" title="InPost status" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe> <p><a href="https://isitdownrightnow.app/services/inpost/">InPost status</a> from IsItDownRightNow.app</p>
Image, updated about every 10 minutes
<a href="https://isitdownrightnow.app/services/inpost/"><img src="https://isitdownrightnow.app/share/inpost.png" alt="InPost status: problem reports over the last 24 hours" width="600" height="315" loading="lazy"></a>
Markdown image, for README files
[![InPost status](https://isitdownrightnow.app/share/inpost.png)](https://isitdownrightnow.app/services/inpost/)

Badge, frame and image load no scripts from other sites and set no cookies; people who see them on your page load them from our server. More for journalists.

How we track InPost

The status on this page comes from user-submitted problem reports for InPost, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for InPost, 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. InPost 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.

Elsewhere

Check other services