Peeringdb down?

Matt Griswold grizz at dipd.com
Thu Jun 28 23:25:36 CDT 2012


FWIW, server move is complete which should mean the end of outages, feel
free to email me or support at peeringdb.com with any outstanding issues.
On Jun 15, 2012 2:08 AM, "Ethern Lin" <ethern at ascc.net> wrote:

> web site is down but traceroute is ok.
>
>                                                    Packets
> Pings
>  Host                                             Loss%   Snt   Last   Avg
>  Best  Wrst StDev
>  1. 140.109.1.1                                    0.0%    10    1.2   3.4
>   1.2   6.4   2.0
>  2. 140.109.255.213                                0.0%    10    0.7   0.7
>   0.4   1.1   0.3
>  3. 202.169.174.77                                 0.0%    10    0.5   0.5
>   0.4   0.9   0.1
>  4. 202.169.174.226                                0.0%    10  130.4 130.6
> 130.4 131.0   0.2
>  5. 64.209.107.45                                  0.0%    10  131.1 141.0
> 130.5 226.0  30.0
>  6. 69.31.111.222                                 20.0%    10  193.5 193.5
> 191.7 195.0   1.4
>  7. 69.31.111.137                                  0.0%    10  193.9 193.8
> 193.7 193.9   0.1
>  8. 69.31.111.6                                    0.0%    10  190.6 190.9
> 190.6 191.3   0.3
>  9. 75.102.0.114                                   0.0%    10  193.0 192.5
> 190.9 198.2   2.1
> 10. 205.234.211.82                                 0.0%    10  191.1 190.8
> 190.4 191.3   0.3
>
> port 80 does open but not work:
>
> % tcptraceroute www.peeringdb.com
> Selected device le0, address 140.109.1.6, port 51755 for outgoing packets
> Tracing the path to www.peeringdb.com (205.234.211.82) on TCP port 80, 30
> hops max
>  1  fe-1-1-br5.ascc.net (140.109.1.1)  6.804 ms  9.758 ms  9.510 ms
>  2  140.109.255.213 (140.109.255.213)  9.994 ms  9.585 ms  10.506 ms
>  3  202.169.174.77 (202.169.174.77)  9.477 ms  9.629 ms  9.992 ms
>  4  202.169.174.226 (202.169.174.226)  130.602 ms  130.264 ms  130.229 ms
>  5  64.209.107.45 (64.209.107.45)  130.324 ms  130.345 ms  133.022 ms
>  6  * * *
>  7  ae1-40g.cr1.ord1.us.nlayer.net (69.31.111.133)  190.646 ms  190.187
> ms  228.519 ms
>  8  po6.ar1.ord1.us.scnet.net (69.31.111.58)  190.645 ms  190.590 ms
>  246.995 ms
>  9  ge0-49.aggr4302.ord2.us.scnet.**net<http://ge0-49.aggr4302.ord2.us.scnet.net>(75.102.0.110)  198.134 ms  199.110 ms  195.075 ms
> 10  www.peeringdb.com (205.234.211.82) [open]  190.322 ms  190.450 ms
>  190.454 ms
>
> % telnet www.peeringdb.com 80
> Trying 205.234.211.82...
> Connected to www.peeringdb.com.
> Escape character is '^]'.
> Connection closed by foreign host.
>
> cheers,
> Ethern
>
> ==============================**========
> Ethern Lin<ethern at ascc.net>
> Network Division
> Computing Center, ACADEMIA SINICA
> AS Number: 9264
> Phone: +886-2-66149953
> TANet VoIP: 93909953
> Fax: +886-2-66146444
> ==============================**========
>
>
> ? 2012/6/15 ?? 02:41, Righa Shake ??:
>
>> Hey,
>>
>> Anybody able to access peeringdb today?
>>
>> Regards,
>> Righa Shake
>>
>> On Fri, Jun 8, 2012 at 7:04 PM, Darius Jahandarie<djahandarie at gmail.**com<djahandarie at gmail.com>
>> >wrote:
>>
>>  On Fri, Jun 8, 2012 at 12:03 PM, Darius Jahandarie
>>> <djahandarie at gmail.com>  wrote:
>>>
>>>> However, when the web interface goes down, usually you can still get
>>>> information with the whois and finger interfaces:
>>>>
>>> And of course, this is what I meant by the finger interface:
>>>
>>> d82h214:~ Darius$ finger as4436 at peeringdb.com
>>>
>>>
>>>
>>> Still early.
>>>
>>> --
>>> Darius Jahandarie
>>>
>>>
>>>
>> --
>> ==============================**========
>> Ethern Lin<ethern at ascc.net>
>> Network Division
>> Computing Center, ACADEMIA SINICA
>> AS Number: 9264
>> Phone: +886-2-66149953
>> TANet VoIP: 93909953
>> Fax: +886-2-66146444
>> ==============================**========
>>
>


More information about the NANOG mailing list