Hacker News new | past | comments | ask | show | jobs | submit login
What Is BGP Visibility, Really? (thousandeyes.com)
44 points by kiyanwang on April 13, 2019 | hide | past | favorite | 7 comments



Alas, at least one v6 block in mozilla's ASN has been unreachable for several months now from my ISP (compared ISP's looking glass and RIPE looking glass)... and there is no avenue to report this. Sending mails to the whois contacts remains unanswered and customer support is utterly incapable of even understanding what I am reporting.


HN is proven to be good support channel for unusual issues. List here src and dst IPs, there is a good chance net ops from various ISPs read HN and may help.


Routing problems aren't particularly "unusual" though. The issue is that sometimes there's no good way to report them and they may go unnoticed for a long time if things like happy eyeballs or dns round robin mask some of their impact.


Can you provide details? Mozilla doesn't do much inbound ipv6 on their own AS, its mostly outbound to other things on the interwebz.


    $ dig AAAA +short irc.mozilla.org
    2620:101:8030:74::1:1b
    $ whois 2620:101:8030:74::1:1b
    NetRange:       2620:101:8000:: - 2620:101:80FF:FFFF:FFFF:FFFF:FFFF:FFFF
    CIDR:           2620:101:8000::/40
    NetName:        MOZILLA-V6-1
    $ ping -6 irc.mozilla.org
    PING irc.mozilla.org(2620:101:8030:74::1:1b (2620:101:8030:74::1:1b)) 56 data bytes
    From 2003:0:8a05:b000::1 (2003:0:8a05:b000::1): icmp_seq=1 Destination unreachable: No route

ISP's looking glass: https://f-lga1.f.de.net.dtag.de/index.php?pageid=lg&query=ip...


Should be fixed now.

RIPEstat now says “2620:101:8030::/47 is visible by 97% of 223 IPv6 RIS full peers.” Yesterday morning it was saying 62%.


Thanks, can confirm.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: