Is InPost Down? Live status & outage reports

Service info and troubleshooting

App Won't Load or Crashes on Launch

If the InPost mobile app freezes on the splash screen or crashes immediately, start with the basics: force-close the app, clear its cache (Settings → Apps → InPost → Clear Cache), and relaunch. If that doesn't help, check whether your OS version is still supported — older Android or iOS versions sometimes lose compatibility after app updates. Reinstalling the app usually resolves persistent crash loops.

Login Fails Despite Correct Credentials

A failed login often comes down to a session conflict or a cached token that's gone stale. Log out from all devices if the option is available, clear the app cache or browser cookies, and try again. If you're using a password manager, double-check that it isn't autofilling an outdated password. Resetting the password through the email link typically clears authentication errors within a few minutes.

Payment Not Going Through at Checkout

• Verify your card details are entered correctly, including the billing postcode
• Check that your bank hasn't blocked the transaction — some banks flag courier service payments as unusual
• Try a different browser or switch from the app to the website at inpost.pl
• Use an alternative payment method such as BLIK or a different card

If BLIK times out, the session window is only 60 seconds — generate a new code and confirm faster.

Parcel Locker QR Code Won't Scan

Poor lighting and a cracked screen protector are the two most common culprits. Increase screen brightness to maximum before presenting the code. If the camera still won't read it, use the manual code entry option instead — the numeric code is always included in the pickup notification.

Push Notifications Not Arriving

• On Android, check that battery optimization isn't killing the app in the background
• On iOS, go to Settings → Notifications → InPost and confirm alerts are enabled
• Make sure the app has permission to run in the background

Without notifications, you may miss the collection window and have the parcel returned.

Website Returning Errors or Loading Slowly

If inpost.pl is throwing 502 or 503 errors, the issue is usually a temporary server spike. Wait a few minutes and refresh. If pages load but content is broken — missing buttons, unstyled layout — clear your browser cache with Ctrl+Shift+Delete and do a hard reload with Ctrl+F5. Switching to a different browser confirms whether it's a local cache issue or something wider.

Tracking Status Not Updating

Tracking data sometimes lags by 30–60 minutes after a parcel changes hands. If the status has been stuck for over 24 hours, copy the parcel number and check it directly on the website rather than in the app — the two data feeds occasionally get out of sync. Contacting support with the parcel ID is the next step if the status remains frozen.