nntp down

Down For Everyone Or Just Me -> Check if your website is down or up? reports “It’s not just you! http://nntp.opensuse.org looks down from here.”
it does not seem to be scheduled, per https://en.opensuse.org/openSUSE:Downtime

traceroute shows:

linux-os114:~ # traceroute nntp.opensuse.org
traceroute to nntp.opensuse.org (130.57.5.118), 30 hops max, 40 byte packets using UDP
 1  192.168.1.1 (192.168.1.1)  0.296 ms   0.223 ms   0.292 ms
 2  ge-1-3-0-1103.hsnqu1.dk.ip.tdc.net (87.55.151.65)  35.524 ms   34.681 ms   33.425 ms
 3  as0-0.nyk2nqp1.us.ip.tdc.net (83.88.29.23)  116.106 ms   116.328 ms   116.088 ms
 4  146.82.35.201 (146.82.35.201)  115.351 ms   115.729 ms   115.612 ms
 5  vlan80.csw3.NewYork1.Level3.net (4.69.155.190)  115.792 ms vlan70.csw2.NewYork1.Level3.net (4.69.155.126)  116.298 ms   115.732 ms
 6  ae-62-62.ebr2.NewYork1.Level3.net (4.69.148.33)  116.419 ms ae-91-91.ebr1.NewYork1.Level3.net (4.69.134.77)  116.417 ms ae-82-82.ebr2.NewYork1.Level3.net (4.69.148.41)  116.282 ms
 7  4.69.201.46 (4.69.201.46)  116.371 ms 4.69.201.38 (4.69.201.38)  116.639 ms ae-4-4.ebr1.NewYork2.Level3.net (4.69.141.18)  116.771 ms
 8  ae-1-51.edge2.NewYork2.Level3.net (4.69.138.195)  116.448 ms   115.998 ms   116.234 ms
 9  4.68.111.138 (4.68.111.138)  131.626 ms 204.255.173.53 (204.255.173.53)  116.709 ms Verizon-level3-2x10g.NewYork.Level3.net (4.68.62.42)  125.491 ms
10  0.so-5-1-0.XT2.DEN4.ALTER.NET (152.63.1.138)  181.863 ms 0.ge-4-1-0.XT1.DEN4.ALTER.NET (152.63.10.178)  178.694 ms   178.609 ms
11  POS6-0.GW3.DEN4.ALTER.NET (152.63.72.69)  178.398 ms   177.874 ms   177.511 ms
12  novell-gw.customer.alter.net (65.206.183.22)  188.600 ms   188.693 ms   191.973 ms
13  192.94.118.247 (192.94.118.247)  191.262 ms   191.830 ms   196.093 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
linux-os114:~ #

just reporting/notifying (not pushing, accusing, complaining, etc)

On 08/13/2013 07:46 AM, DenverD wrote:
>
> Down

now up…thank you to the fixers.


dd

On Tue, 13 Aug 2013 05:46:01 +0000, DenverD wrote:

> ‘Down For Everyone Or Just Me -> Check if your website is down or up?’

That site only checks port 80/443 IIRC, so it’s not a good test for other
ports.

From your traceroute, it looks like it was something on the way - maybe
compare to one now that you can reach it.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

On 08/13/2013 07:15 PM, Jim Henderson wrote:
> That site only checks port 80/443 IIRC, so it’s not a good test for other
> ports.

[laughing] yes, i learned that after i posted…but, i still was
unable to connect through Thunderbird…but, that could have been an
ISP thing (they keep going up on the price and down in reliability)

> From your traceroute, it looks like it was something on the way - maybe
> compare to one now that you can reach it.


linux-os114:~ # traceroute nntp.opensuse.org
traceroute to nntp.opensuse.org (130.57.5.118), 30 hops max, 40 byte
packets using UDP
1  192.168.1.1 (192.168.1.1)  0.296 ms   0.086 ms   0.172 ms
2  ge-1-3-0-1103.hsnqu1.dk.ip.tdc.net (87.55.151.65)  22.057 ms
21.369 ms   21.408 ms
3  as0-0.nyk2nqp1.us.ip.tdc.net (83.88.29.23)  116.095 ms   115.739
ms   116.009 ms
4  146.82.35.201 (146.82.35.201)  116.072 ms   116.095 ms   116.139 ms
5  vlan90.csw4.NewYork1.Level3.net (4.69.155.254)  116.168 ms
116.712 ms vlan60.csw1.NewYork1.Level3.net (4.69.155.62)  116.124 ms
6  ae-82-82.ebr2.NewYork1.Level3.net (4.69.148.41)  116.521 ms
ae-71-71.ebr1.NewYork1.Level3.net (4.69.134.69)  116.243 ms
ae-72-72.ebr2.NewYork1.Level3.net (4.69.148.37)  116.254 ms
7  4.69.201.42 (4.69.201.42)  116.134 ms
ae-48-48.ebr2.NewYork2.Level3.net (4.69.201.50)  116.179 ms
ae-45-45.ebr2.NewYork2.Level3.net (4.69.141.22)  119.213 ms
8  ae-2-52.edge2.NewYork2.Level3.net (4.69.138.227)  116.232 ms
ae-1-51.edge2.NewYork2.Level3.net (4.69.138.195)  116.424 ms
ae-2-52.edge2.NewYork2.Level3.net (4.69.138.227)  116.139 ms
9  4.68.111.138 (4.68.111.138)  131.382 ms
Verizon-level3-2x10g.NewYork.Level3.net (4.68.62.42)  116.825 ms
0.ae12.BR2.NYC4.ALTER.NET (204.255.173.53)  116.728 ms
10  0.so-5-1-0.XT2.DEN4.ALTER.NET (152.63.1.138)  179.599 ms
0.ge-4-1-0.XT1.DEN4.ALTER.NET (152.63.10.178)  177.783 ms   183.910 ms
11  POS6-0.GW3.DEN4.ALTER.NET (152.63.72.69)  175.558 ms
POS7-0.GW3.DEN4.ALTER.NET (152.63.72.73)  179.773 ms
POS6-0.GW3.DEN4.ALTER.NET (152.63.72.69)  176.533 ms
12  novell-gw.customer.alter.net (65.206.183.22)  191.910 ms
195.890 ms   192.077 ms
13  192.94.118.247 (192.94.118.247)  194.893 ms   191.167 ms   191.892 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
linux-os114:~ #

hmmmm…looks almost identical…maybe it was a TB problem? which i
wrongly assumed was a nntp down problem because i used the wrong tool
to dig…

sigh.


dd

On Tue, 13 Aug 2013 18:18:26 +0000, dd wrote:

> hmmmm…looks almost identical…maybe it was a TB problem? which i
> wrongly assumed was a nntp down problem because i used the wrong tool to
> dig…

Could be.

Traceroute from here stops at the same place, could be that it’s just
filtered at that point. tcptraceroute shows the same thing, other than a
response from nntp.opensuse.org.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

On 2013-08-13 20:18, dd wrote:
> On 08/13/2013 07:15 PM, Jim Henderson wrote:
>> That site only checks port 80/443 IIRC, so it’s not a good test for other
>> ports.
>
> [laughing] yes, i learned that after i posted…but, i still was unable
> to connect through Thunderbird…but, that could have been an ISP thing
> (they keep going up on the price and down in reliability)

You can select the port for a traceroute.

(OT)

A friend of mine related to me the history of internet in my own country
as seen from my now ISP. Apparently, at first they charged, or wanted to
charge, for each port you used. Also, they charged per number of emails
sent, and wanted to charge more per distance. How can an email sent to
your neighbor cost the same as to the antipodes! Crazy!

POT people! :wink:

(My friend says a business will charge for everything people will be
prepared to pay, and as much as possible, till a competitor or regulator
changes the field. So things as charging per email come into being)


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

On 08/13/2013 08:59 PM, Jim Henderson wrote:
> tcptraceroute

oh! nice tool (i just installed, thanks)


dd