External Resource Monitoring: Track Third-Party Dependencies
Your website is only as reliable as its dependencies. Monitor CDNs, fonts, scripts, and other external resources that can break your site even when your server is up.
Traditional uptime monitoring only checks if your server responds. But modern websites depend on dozens of external services: jQuery from CDN, Google Fonts, analytics scripts, Bootstrap CSS. If any of these fail, users see a broken page — and upsonar catches that.
The Hidden Problem
Your server is up, but users see a broken page.
The Scenario
Your server returns HTTP 200 OK. Traditional monitoring says "all good." But your users see a blank page because:
- jQuery CDN is down — your JavaScript doesn't run
- Google Fonts returns 403 — your text looks wrong
- Analytics script times out — page load stalls
- CDN returns stale/corrupted files
Real-World Impact
Resources We Monitor
Everything your page loads.
| Resource Type | HTML Element | Examples |
|---|---|---|
| JavaScript | <script src> | jQuery, React, analytics |
| Stylesheets | <link rel="stylesheet"> | Bootstrap, Tailwind CDN |
| Fonts | <link>, @font-face | Google Fonts, Adobe Fonts |
| Images | <img src> | CDN-hosted images |
| Preloaded | <link rel="preload"> | Critical resources |
We automatically detect resources from external domains. Resources from your own domain are not tracked separately — they're covered by the main availability check.
How It Works
Add Your Website
When you add a website URL, upsonar fetches the page and analyzes the HTML to discover all external resources.
Resource Discovery
We parse script tags, stylesheets, fonts, images, and preload hints to build a list of third-party dependencies your page needs.
Continuous Monitoring
Each check verifies not just your main page, but also all discovered resources. We track response codes, response times, and availability.
Incident on Failure
When a resource fails (404, 403, 500, timeout), an incident is created with full details. You're notified immediately.
Why Monitor External Resources?
Catch CDN Outages
Know immediately when Cloudflare, Fastly, or other CDNs have issues.
Detect Blocked Resources
Some countries or networks block certain CDNs. See regional issues.
Track Response Times
Identify slow resources that hurt your page load performance.
Find Broken Links
Detect 404 errors when CDNs remove old versions of libraries.
Resource Performance Tracking
Monitor response times over time.
Hourly Statistics
Track resource performance trends
upsonar aggregates response times into hourly statistics, so you can identify resources that are consistently slow or have periodic issues.
| Plan | History Retention |
|---|---|
| Echo (Free) | 1 day |
| Pulse | 3 days |
| Wave | 7 days |
Multi-Region Resource Checks
Catch regional CDN issues.
Check From Multiple Locations
CDN issues often affect specific regions
A CDN might be working perfectly in the US but failing in Europe. With multi-region checks, you see exactly where resources are failing — not just that they failed.
More Regions = Better Coverage
Resource Degradation Incidents
Full diagnostics when resources fail.
Current Status
When external resources fail, upsonar creates a "Resource Degradation" incident with:
Failed Resources
List of which resources failed and their individual status.
Error Details
HTTP status codes, error messages, timeout information.
Affected Regions
Which check regions detected the failure.
Extended Diagnostics
Response headers and body for debugging (paid plans).
Common External Resource Issues
CDN blocking requests due to hotlink protection, geographic restrictions, or rate limiting. Common with Google Fonts in some countries.
Resource was removed or URL changed. Common when CDNs deprecate old library versions or when third-party services shut down.
CDN is overloaded or experiencing network issues. Your page may load very slowly or appear broken while waiting for the resource.
CDN or origin server is having internal issues. Usually temporary but can significantly impact your site's functionality.