5 ms·

This explains a lot. Initially thought my mobile phone Internet connectivity was flakey because I couldn't access HN here in Australia, whilst it's fine over wi

This explains a lot. Initially thought my mobile phone Internet connectivity was flakey because I couldn't access HN here in Australia, whilst it's fine over wi-fi (wired Internet).

abhishekjha 6y ago
Its reverse for me. The broadband fails to connect to HN but my mobile ISP is able to reach it fine.
- josephb 6y ago
  Because networks are connected to others via different paths, it's not unusual that one method of connectivity would work and one doesn't. Also the Internet has lots of asymmetric traffic, just because a forward path towards a destination may look the same from different networks, it doesn't mean the reverse path will be similar.
- willis936 6y ago
  Same for me in midwest US. I first thought I had broken my DNS filter again through regular maintenance updates, then I suspected my ISP/modem because it regularly goes out. I have never seen the behavior I saw this morning: some sites failing to resolve.
  - bmlzootown 6y ago
    I thought Cloudflare was having issues again, since I use their DNS servers, so I started by changing that. Then I tried restarting everything, modem/router/computer. Wasn't until I connected to a VM that a friend hosts that I was finally able to access HN, and thus saw this thread. Hopefully this will get fixed within a reasonable timespan.
- every 6y ago
  ycombinator.com pinged just fine but news.ycombinator.com dropped 100% packets. But all better now...
abafazi 6y ago
Reverse for me
yreg 6y ago
I was so pissed at Waze earlier for giving up on me in a critical moment. Then I found out I'm also unable to send iMessages, but I was curious, since I could browse the web just fine. When something doesn't work I always assume it's a problem with my device/configuration/connection. Who would have thought it's a global event such as the repeated Facebook SDK issues.
bonestamp2 6y ago
Yep, I had a similar experience. Sites that didn't work from my home connection worked fine on mobile. After rebooting and it persisted, I assumed it was just a DNS or routing issue since they were both connecting to different networks.

This explains a lot. Initially thought my mobile phone Internet connectivity was flakey because I couldn't access HN here in Australia, whilst it's fine over wi-fi (wired Internet).

abhishekjha 6y ago

Its reverse for me. The broadband fails to connect to HN but my mobile ISP is able to reach it fine.

josephb 6y ago
Because networks are connected to others via different paths, it's not unusual that one method of connectivity would work and one doesn't. Also the Internet has lots of asymmetric traffic, just because a forward path towards a destination may look the same from different networks, it doesn't mean the reverse path will be similar.
willis936 6y ago
Same for me in midwest US. I first thought I had broken my DNS filter again through regular maintenance updates, then I suspected my ISP/modem because it regularly goes out. I have never seen the behavior I saw this morning: some sites failing to resolve.
- bmlzootown 6y ago
  I thought Cloudflare was having issues again, since I use their DNS servers, so I started by changing that. Then I tried restarting everything, modem/router/computer. Wasn't until I connected to a VM that a friend hosts that I was finally able to access HN, and thus saw this thread. Hopefully this will get fixed within a reasonable timespan.
every 6y ago
ycombinator.com pinged just fine but news.ycombinator.com dropped 100% packets. But all better now...

abafazi 6y ago

Reverse for me

yreg 6y ago

I was so pissed at Waze earlier for giving up on me in a critical moment. Then I found out I'm also unable to send iMessages, but I was curious, since I could browse the web just fine. When something doesn't work I always assume it's a problem with my device/configuration/connection. Who would have thought it's a global event such as the repeated Facebook SDK issues.

bonestamp2 6y ago

Yep, I had a similar experience. Sites that didn't work from my home connection worked fine on mobile. After rebooting and it persisted, I assumed it was just a DNS or routing issue since they were both connecting to different networks.