Dependency-Aware Uptime Monitor
0
Monitor your services and third-party APIs with intelligent alerts that distinguish your outages from theirs.
Added Jan 4, 2026
5 signals
The Problem
Developers and businesses waste hours debugging local issues that are actually third-party outages (Cloudflare, payment gateways, DNS). Conversely, they often discover their own services are down only after customer complaints. Existing tools monitor either internal infrastructure OR public services, but never correlate both to provide actionable intelligence about root cause.
Potential Solution
Detailed solution approach available for premium members.
Why Now?
Market timing analysis available for premium members.
Aeromexico. Extremely difficult to book with from the UK?
I tried booking flights from Heathrow to Mexico City last night but my card wasn't accepted. I tried another card but I kept getting error messages (no issue with my cards) I tried clearing cache then trying on the app or a different browser. No joy. Eventually I had to phone to make the payment. The person I spoke with then emailed me the wrong return date... he didn't seemed bothered by the error but for me it was stressful! Thankfully he quickly amended the email to shpe the correct return date! I've flown with them before after my BA flight to mexico was cancelled and I was impressed by their modern planes and good customer service. It's strange how glitchy the website is.
Subdomains refuse to resolve - Nginx/Tailscale/TrueNAS/AWS
**Current Setup** * TrueNAS Scale ElectricEel 24.10 - UI configured for 81 and 444 * Nginx-proxy-manager 2.13.5/1.2.23 as an application on TrueNAS. Configured to listen on 80 and 443. Proxy hosts are set up pointing to applications. * Tailscale * AWS Route 53 hosted domain. A record points to TS IP for the server, CNAME record for wildcards pointing to the canonical name of the TrueNAS server. **The Problem** DNS resolves without problem when subdomains aren't involved. mydomain.com points to my TrueNAS UI, which is fine. Applications can be accessed by mydomain.com:portNumber but anytime I try to access by subdomain (myapp.mydomain.com) I get: ERR_NAME_NOT_RESOLVED. **Current Best Guess** It's possible that Nginx isn't actually listening on 80 or 443. A netstat -tpln shows the program name "nginx:master" listening on some of the ports that would be expected, such as 32015, 32016, 444, and 81, however all of the other ports serving applications including 80 and 443 have an application name of "docker-proxy". I'm inclined to believe this means that there's something else listening there, not the least of which could be pihole which is also running as an application. This would make sense, except it continues to return that PID even when Pihole is stopped. I don't know how I would confirm this otherwise, or what would be needed to free up those ports. Trying to look up more information via PS just shows that it's the docker-proxy serving on that port. I haven't had any luck configuring this [version of Nginx](https://jc21.com/projects/nginx-proxy-manager-2/) to generate logs. This could be in part because there are no logs being generated because docker-proxy is hijacking and failing to resolve all of the requests instead of delivering them to Nginx. I'm inclined to believe everything in Route 53 is fine since running dig for both the A record and CNAME bring back the expected results except for: ;; communications error to 192.168.xx.yy#zz: connection refused ;; communications error to 192.168.xx.yy#zz: connection refused ;; communications error to 192.168.xx.yy#zz: connection refused **What's my next best step to diagnose and/or resolve this issue?**
Issues Logging in with ipostal1.com?
I can’t find any information about issues logging into ipostal1.com online, but wondering if anyone else here has encountered this today and yesterday. I’m open to suggestions for alternative international mailing options as my first experience with this company is unfortunately negative and has made me lose trust in this company’s operations. I’m trying to log in and encounter the following error: {"header":{"statusCode":500,"message":"Server Error","link":"","debug":{"message":"Server Error! please contact support","route":"app_web_webinbox_inbox","parameters":{"page_name":"payment_method","x-session-token":null,"x-api-key":null,"uri":"\/mailbox?page_name=payment_method"}}},"data":[]}
I need help with WEBSOCKET SUPPORT!!
I’m attempting to expose my local web service through Nginx Proxy Manager or Traefik. However, I consistently receive a “WebSocket support” error despite WebSockets being enabled. Please help me troubleshoot and correct the proxy configuration.
+7 more signals