- Service Status
- /
- Poshmark
Is Poshmark Down?
- Poshmark's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 4518 ms
Right now
The verdict is the worse of these two. How we decide
Poshmark's status page
status.poshmark.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Poshmark Mobile Apps | Operational |
| Poshmark Website | Operational |
| Checkout | Operational |
| Support Communications | Operational |
| United States Redemptions | Operational |
| Canada Redemptions | Operational |
| United States Posh Authenticate | Operational |
| Canada Posh Authenticate | Operational |
| Push Notifications | Operational |
| Email Notifications | Operational |
| United States Shipping | Operational |
| Canada Shipping | Operational |
FlareWarden checks
poshmark.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 4518 ms
- Checked
By region
- Ashburn reachable, 6595 ms
- Dallas reachable, 4304 ms
- Frankfurt reachable, 3515 ms
- Johannesburg reachable, 5586 ms
- Los Angeles reachable, 3442 ms
- Newark reachable, 3371 ms
- Paris reachable, 5261 ms
- São Paulo reachable, 4071 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 125 ms | 1 ms | 16 ms | 3953 ms |
| Dallas | 92 ms | 0 ms | 2 ms | 4192 ms |
| Frankfurt | 15 ms | 1 ms | 4 ms | 3035 ms |
| Johannesburg | 238 ms | 0 ms | 2 ms | 4690 ms |
| Los Angeles | 50 ms | 1 ms | 5 ms | 3376 ms |
| Newark | 19 ms | 20 ms | 22 ms | 3202 ms |
| Paris | 36 ms | 1 ms | 3 ms | 4305 ms |
| São Paulo | 139 ms | 1 ms | 2 ms | 3548 ms |
History
Incidents Poshmark reported
Since Oct 22, 1 day · from status.poshmark.com
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
Poshmark website availability
Measured by FlareWarden · poshmark.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 4405ms
Last 30 days
67-day clean streakMeasured by FlareWarden's own checks of poshmark.com from multiple regions every 6 hours. Poshmark's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 67 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Poshmark does
Poshmark is a resale marketplace for clothing, shoes and accessories, where sellers list from their own closets and buyers browse a feed built around sharing and following. Naver owns it. For the people who sell on it full time it is a storefront and an income, so an outage during a posting party or a weekend rush costs real sales rather than convenience.
What an outage looks like
Listings fail to publish or upload photos, and shares and follows silently do nothing. The feed loads empty or shows stale items. Checkout errors at payment, so buyers abandon carts on listings that look available. Shipping label generation fails, leaving sold items unshippable. Push and email notifications for offers and sales stop, so sellers miss time-limited offers entirely.
What to do about it
Poshmark runs a status page at status.poshmark.com that breaks the service into mobile apps, website, checkout, shipping, and push and email notifications, with incident history alongside. Match your symptom to a component there. Label problems are frequently carrier-side rather than Poshmark-side, so check whether the incident names a carrier before contacting support about a sale you cannot ship.
Is it down for everyone, or just you?
If this page says Poshmark is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Poshmark outage FAQ
Is Poshmark down or is it just my app?
A buyer paid but I cannot print a shipping label. What now?
Will my listing publish if it failed during an outage?
Do offers and sales still count if notifications stop?
How we measure this
- We request Poshmark's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Poshmark publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Poshmark itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Poshmark goes down
We check Poshmark every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring
