[outages] fb.me is down

Sun May 19 01:20:02 EDT 2013

On Sat, May 18, 2013 at 09:45:18PM -0700, Constantine A. Murenin wrote:
> I've noticed it didn't work yesterday, either.
> 
> Tested from two locations.
> 
> 
> California:
> 
> li16x-xxx:~# telnet fb.me http
> Trying 2a03:2880:2110:df01:face:b00c:0:8...
> ^C
> li16x-xxx:~# traceroute6 fb.me
> traceroute to fb.me (2a03:2880:2110:df01:face:b00c:0:8), 30 hops max, 80 byte packets
>  1  2600:3c01:ffff:0:ca4c:75ff:fef5:d63f (2600:3c01:ffff:0:ca4c:75ff:fef5:d63f)  206.674 ms  206.681 ms  206.639 ms
>  2  10gigabitethernet2-3.core1.fmt1.he.net (2001:470:1:1db::1)  0.668 ms  0.660 ms  0.653 ms
>  3  10gigabitethernet1-2.core1.sjc2.he.net (2001:470:0:2f::2)  0.850 ms  0.842 ms  0.973 ms
>  4  2001:504:0:1:0:3:2934:2 (2001:504:0:1:0:3:2934:2)  1.758 ms  51.504 ms 2001:470:0:14a::2 (2001:470:0:14a::2)  0.907 ms
>  5  ae0.bb01.sjc1.tfbnw.net (2620:0:1cff:dead:beef::9)  1.065 ms ae1.bb01.sjc1.tfbnw.net (2620:0:1cff:dead:beef::15)  1.953 ms  1.454 ms
>  6  ae6.bb01.frc1.tfbnw.net (2620:0:1cff:dead:beef::aa)  69.617 ms  69.712 ms  69.723 ms
>  7  ae1.dr02.frc1.tfbnw.net (2620:0:1cff:dead:beef::93)  67.326 ms ae2.dr04.frc1.tfbnw.net (2620:0:1cff:dead:beef::1de)  66.698 ms ae2.dr02.frc1.tfbnw.net (2620:0:1cff:dead:beef::9b)  66.627 ms
>  8  po1019.csw13b.frc1.tfbnw.net (2620:0:1cff:dead:beef::12bd)  68.058 ms  67.433 ms  67.786 ms
>  9  * * *
> 10  * * *
> 11  * * *
> 
> 
> Europe:
> 
> Cns# telnet -6 fb.me http
> Trying 2a03:2880:2110:df01:face:b00c:0:8...
> ^C
> Cns# traceroute6 fb.me
> traceroute6 to fb.me (2a03:2880:2110:df01:face:b00c:0:8) from 2001:470:XXXX::, 64 hops max, 12 byte packets
>  1  cnst-3.tunnel.tserv6.fra1.ipv6.he.net  9.78 ms  9.188 ms  8.916 ms
>  2  gige-g2-20.core1.fra1.he.net  10.158 ms  6.491 ms  6.453 ms
>  3  ae1.br01.fra1.tfbnw.net  29.037 ms  7.278 ms  6.869 ms
>  4  ae1.bb01.fra2.tfbnw.net  7.048 ms  6.844 ms  6.812 ms
>  5  ae11.bb02.iad2.tfbnw.net  94.231 ms  93.68 ms  94.441 ms
>  6  ae4.bb02.frc1.tfbnw.net  107.464 ms  107.978 ms  116.968 ms
>  7  ae2.dr01.frc1.tfbnw.net  104.31 ms ae40.dr01.frc1.tfbnw.net  103.572 ms ae40.dr02.frc1.tfbnw.net  124.374 ms
>  8  ae2.dr02.frc1.tfbnw.net  103.912 ms po1021.csw13b.frc1.tfbnw.net  104.85 ms  105.569 ms
>  9  * * *
> 10  * * *
> 11  * * *
> 
> 
> I have no explanation how they could possibly be down for more than a day, 
> even if only on IPv6; perhaps only he.net is affected?

Taken from my home machine (Mountain View, CA; Comcast connection); only
IPv4, sorry:

$ telnet fb.me 80
Trying 173.252.110.27...
Connected to fb.me.
Escape character is '^]'.
GET / HTTP/1.0
Host: fb.me

HTTP/1.0 301 Moved Permanently
Location: http://www.facebook.com/
Content-Type: text/html; charset=utf-8
X-FB-Debug: QataDVOUSq+vNlfgI3enUcTGQ86k+aJ3APJ2ledddJw=
Date: Sun, 19 May 2013 05:17:48 GMT
Connection: close
Content-Length: 0

Connection closed by foreign host.

$ mtr fb.me
                                                  Packets               Pings
 Host                                           Loss%   Snt   Rcv  Last   Avg  Best  Wrst
 1. gw.home.lan                                  0.0%    11    11   0.4   0.3   0.2   0.4
 2. c-67-180-84-1.hsd1.ca.comcast.net            0.0%    11    11  16.6  24.6   9.2  40.0
 3. te-0-0-0-12-ur05.santaclara.ca.sfba.comcast  0.0%    11    11   9.2  10.2   9.2  11.7
 4. te-1-1-0-6-ar01.sfsutro.ca.sfba.comcast.net  0.0%    10    10  13.5  14.7  11.9  24.9
 5. he-1-8-0-0-cr01.sanjose.ca.ibone.comcast.ne  0.0%    10    10  13.7  16.6  13.7  23.0
 6. xe-10-2-0.edge1.SanJose1.Level3.net          0.0%    10    10  43.3  37.2  22.3  54.7
 7. vlan70.csw2.SanJose1.Level3.net              0.0%    10    10  79.6  81.6  79.4  91.4
 8. ae-72-72.ebr2.SanJose1.Level3.net            0.0%    10    10  81.3  81.0  79.5  81.7
 9. ae-2-2.ebr2.SanJose5.Level3.net              0.0%    10    10  81.9  81.0  79.4  82.6
10. ae-6-6.ebr2.LosAngeles1.Level3.net           0.0%    10    10  80.2  80.7  79.9  81.4
11. ae-3-3.ebr3.Dallas1.Level3.net               0.0%    10    10  81.6  81.1  79.8  81.6
12. ae-73-73.csw2.Dallas1.Level3.net             0.0%    10    10  80.6  80.9  80.0  83.0
13. ae-71-71.ebr1.Dallas1.Level3.net             0.0%    10    10  80.0  82.4  80.0  92.0
14. ae-2-2.ebr1.Miami1.Level3.net                0.0%    10    10  81.8  84.0  80.0  95.2
15. ae-1-51.edge4.Miami1.Level3.net              0.0%    10    10  79.8  89.5  79.8 130.2
16. TRINITY-COM.edge4.Miami1.Level3.net          0.0%    10    10  87.9  88.3  87.0  92.3
17. ???
18. 24.244.158.2                                 0.0%    10    10  87.8  88.2  86.6  90.0
19. 208-87-35-103.securehost.com                 0.0%    10    10  87.4  87.7  86.8  88.3

Seems ICMP traceroute should work to them, at least for IPv4.

I can try from another destination if needed.

Can you determine if this is a IPv6 vs. IPv4 thing?

-- 
| Jeremy Chadwick                                   jdc at koitsu.org |
| UNIX Systems Administrator                http://jdc.koitsu.org/ |
| Mountain View, CA, US                                            |
| Making life hard for others since 1977.             PGP 4BD6C0CB |