# Issues with symbolicating JS and mobile errors

- Provider: [Bugsnag](https://down.guide/providers/bugsnag)
- Confidence: Confirmed
- Impact: Degraded
- lasted 6h 33m
- started 2024-09-30 16:03 UTC
- BugSnag Upload API
- id: DWN-c41695c0db
- Official page: https://stspg.io/kdfzxrb7rmpg

## Updates from Bugsnag
### 2024-09-30 16:03 UTC: monitoring
Some mapping files uploaded between 10 and 11 AM UTC may not be available for the symbolication of events. Resolution is underway to make these available and is complete for Proguard, .so mappings, and soon dSYMs. Processing of all affected source maps will take a little longer. Any uploads since 11 AM UTC are not affected.

### 2024-09-30 22:36 UTC: resolved
This incident has been resolved.

From the builder: does your app depend on Bugsnag? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=bugsnag) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Bugsnag.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-c41695c0db), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.