| Posted by SeanK, 11-01-2004, 02:29 PM | |
I can't get on my box or servint's site! Anyone else having problems?
|
| Posted by DNC80, 11-01-2004, 02:30 PM | |
Same here. Tried my site and the forums.
|
| Posted by albatroz, 11-01-2004, 02:31 PM | |
Me too!. Trying to get there from SouthAmerica unsuccessfully.
|
| Posted by dean-ircomdesign, 11-01-2004, 02:31 PM | |
Seems their network is down.
|
| Posted by bear, 11-01-2004, 02:32 PM | |
From here it looks like a router issue in the Northeast...100% packet loss between Albany and Rochester in NY state.
|
| Posted by deborahsmith, 11-01-2004, 02:32 PM | |
It crashed in Chicago for me.
It was real spotty all the way through Chicago then nothing.
Wait and see. Must be a Peer outage somewhere.
|
| Posted by IGobyTerry, 11-01-2004, 02:33 PM | |
My monitors are going off detecting that the Servint Network is down. I'm unable to reach it here, is anyone else noticing this?
|
| Posted by HSRGeorge, 11-01-2004, 02:34 PM | |
traceroute to 216.22.0.103 (216.22.0.103), 64 hops max, 44 byte packets
1 customer-reverse-entry.64.151.97.25 (64.151.97.25) 0.185 ms 0.254
ms 0.305 ms
2 border-core1-ge7-0.sfo2.servepath.net (69.59.136.49) 0.520 ms
0.611 ms 0.435 ms
3 border1-pos5-1-0.sfo2.servepath.net (216.93.189.33) 1.144 ms 1.012
ms 0.931 ms
4 209.213.192.122 (209.213.192.122) 2.644 ms 3.109 ms 2.802 ms
5 * sntcca2lch2-gige3-2.wcg.net (64.200.150.125) 2.822 ms 3.134 ms
6 sntcca1wcx2-pos11-0.wcg.net (64.200.240.221) 2.721 ms 2.966 ms
2.679 ms
7 dnvrco1wcx3-pos14-0.wcg.net (64.200.240.181) 46.363 ms 46.112 ms
46.522 ms
8 brvwil1wcx3-pos2-0-oc192.wcg.net (64.200.240.122) 51.194 ms 51.895
ms 51.238 ms
9 chcgil9lch1-pos7-1.wcg.net (64.200.210.118) 51.855 ms 51.628 ms
52.393 ms
10 * sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 3.730 ms 3.657 ms
11 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 4.464 ms 3.651 ms
4.180 ms
12 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 4.019 ms 3.637 ms
3.559 ms
13 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 4.268 ms 3.775 ms
4.433 ms
14 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 4.150 ms 4.602 ms
4.055 ms
15 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 4.896 ms 4.502 ms
4.058 ms
16 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 4.767 ms 4.119 ms
4.283 ms
17 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 4.650 ms 4.882 ms
4.686 ms
18 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 4.664 ms 4.553 ms
4.685 ms
19 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 5.402 ms 4.969 ms
4.558 ms
20 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 5.013 ms 4.907 ms
4.561 ms
21 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 5.151 ms 5.162 ms
5.311 ms
22 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 5.151 ms 5.039 ms
5.561 ms
23 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 5.527 ms 5.166 ms
5.408 ms
24 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 5.523 ms
sntcca1wcx2-pos11-0.wcg.net (64.200.240.221) 2.880 ms !H *
25 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 5.978 ms 5.568 ms
5.801 ms
26 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 5.768 ms 6.237 ms
5.554 ms
27 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 6.407 ms 5.779 ms
6.180 ms
28 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 5.641 ms 5.764 ms
6.057 ms
29 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 6.017 ms 6.401 ms
6.305 ms
30 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 6.268 ms 6.029 ms
6.054 ms
31 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 6.398 ms 6.623 ms
6.660 ms
32 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 6.524 ms 6.526 ms
6.559 ms
33 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 6.773 ms 7.032 ms
6.682 ms
34 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 6.525 ms 6.778 ms
6.808 ms
35 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 7.023 ms 7.284 ms
7.061 ms
36 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 7.149 ms 7.035 ms
7.309 ms
37 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 7.516 ms 7.519 ms
7.554 ms
38 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 7.266 ms 7.274 ms
7.180 ms
39 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 7.892 ms 7.648 ms
7.680 ms
40 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 8.022 ms 7.902 ms
7.933 ms
41 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 8.272 ms 8.413 ms
8.182 ms
42 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 8.148 ms 7.882 ms
8.049 ms
43 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 8.771 ms 8.393 ms
8.183 ms
44 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 8.392 ms 8.511 ms
8.681 ms
45 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 8.399 ms 8.531 ms
8.818 ms
46 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 8.444 ms 8.188 ms
8.676 ms
47 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 8.891 ms 8.764 ms
8.917 ms
48 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 8.639 ms 9.002 ms
8.553 ms
49 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 9.267 ms 9.003 ms
9.675 ms
50 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 8.762 ms 9.012 ms
9.060 ms
51 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 9.499 ms 9.114 ms
9.434 ms
52 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 9.880 ms 9.225 ms
9.524 ms
53 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 9.764 ms 9.385 ms
9.677 ms
54 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 9.890 ms 9.524 ms
10.051 ms
55 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 10.263 ms 10.150 ms
9.928 ms
56 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 9.765 ms 9.519 ms
9.926 ms
57 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 10.390 ms 10.271 ms
10.177 ms
58 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 10.390 ms 10.239 ms
10.426 ms
59 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 10.514 ms 10.889 ms
10.552 ms
60 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 10.658 ms 10.464 ms
10.508 ms
61 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 10.748 ms 10.836 ms
10.923 ms
62 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 10.891 ms 10.752 ms
10.926 ms
63 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 10.889 ms 11.397 ms
10.917 ms
64 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 10.999 ms 10.749 ms
10.925 ms
|
| Posted by SeanK, 11-01-2004, 02:34 PM | |
anyone have the 800#
|
| Posted by M7I, 11-01-2004, 02:34 PM | |
Same Here.
|
| Posted by maxcjho, 11-01-2004, 02:34 PM | |
My servint vps is down, too.
|
| Posted by deborahsmith, 11-01-2004, 02:35 PM | |
Ditto.
Comcast Broadband from Michigan. Cant get through Chicago for some reason. Dropped on my head!
Did anyone call over there? I hate to bug them if there is an issue.
|
| Posted by NeonHQ, 11-01-2004, 02:35 PM | |
Just asking.
Is ServInt down at the moment?
I cant access. Not sure is it at my end.
I have a vps with them...
|
| Posted by HSRGeorge, 11-01-2004, 02:35 PM | |
Support line is busy and their dns seems to be bad also, so I can't send an email...
|
| Posted by roccol, 11-01-2004, 02:36 PM | |
Same here. They have had their share of network issues lately.
|
| Posted by The Neoracle, 11-01-2004, 02:37 PM | |
I have 2 VPS, both are down. Can't get to their forums either.
|
| Posted by HSRGeorge, 11-01-2004, 02:37 PM | |
Its another weird dns issue. support line is busy, dns is bad so i can't get an email thru.
|
| Posted by Ash, 11-01-2004, 02:37 PM | |
http://www.webhostingtalk.com/showth...hreadid=338568
http://www.webhostingtalk.com/showth...hreadid=338570
|
| Posted by IGobyTerry, 11-01-2004, 02:39 PM | |
A DNS issue shouldn't be effecting people who run their own offsite DNS servers. This is a network issue that is effecting their connectivity.
|
| Posted by Gizzy, 11-01-2004, 02:39 PM | |
Out in Portland, OR; was in the middle of coding at that lol...
Only number that i can locate is:
(703) 847-1381
Last edited by Gizzy; 11-01-2004 at 02:45 PM.
|
| Posted by blueface, 11-01-2004, 02:40 PM | |
Now that's what I'm worried about ServInt relying on single BTN line without any backup line
|
| Posted by SeanK, 11-01-2004, 02:40 PM | |
ServInt guarantees at least 99.9% uptime, but most importantly we guarantee your satisfaction as we have with thousands of customers for the past 9 years.
|
| Posted by IGobyTerry, 11-01-2004, 02:41 PM | |
Spare me if they're even thinking of bringing WilTel back as I see in that trace.
|
| Posted by SanSui, 11-01-2004, 02:41 PM | |
I can't access anything Servint related either, just within the past 15-20 minutes.
Is this a problem on their end or an internet problem?
|
| Posted by brazosit, 11-01-2004, 02:43 PM | |
My server is down as well. Running a tracert right now.
I have tried calling their 800 number but just get 2 rings and a hangup!
Let us know what is going on!
|
| Posted by DNC80, 11-01-2004, 02:43 PM | |
If you have any questions, you can contact our Network Operations Center at "noc@servint.com", or for emergencies, you can call us at 1-800-573-7846 (press 4 then press 1).
|
| Posted by deborahsmith, 11-01-2004, 02:44 PM | |
Gotta be network connectivity. Just gotta hold off until we hear something. I am sure they are scrambling over there.
Got my full backups from this morning right next to me. No worries.
|
| Posted by bear, 11-01-2004, 02:45 PM | |
Amen to that...right there with you.
|
| Posted by roccol, 11-01-2004, 02:45 PM | |
servint.com is down. So not much point in sending an email there right now.
|
| Posted by HSRGeorge, 11-01-2004, 02:46 PM | |
DNS... for IP's. traceroutes go in endless circles. See below:
traceroute to 216.22.0.103 (216.22.0.103), 64 hops max, 44 byte packets
1 customer-reverse-entry.64.151.97.25 (64.151.97.25) 0.185 ms 0.254
ms 0.305 ms
2 border-core1-ge7-0.sfo2.servepath.net (69.59.136.49) 0.520 ms
0.611 ms 0.435 ms
3 border1-pos5-1-0.sfo2.servepath.net (216.93.189.33) 1.144 ms 1.012
ms 0.931 ms
4 209.213.192.122 (209.213.192.122) 2.644 ms 3.109 ms 2.802 ms
5 * sntcca2lch2-gige3-2.wcg.net (64.200.150.125) 2.822 ms 3.134 ms
6 sntcca1wcx2-pos11-0.wcg.net (64.200.240.221) 2.721 ms 2.966 ms
2.679 ms
7 dnvrco1wcx3-pos14-0.wcg.net (64.200.240.181) 46.363 ms 46.112 ms
46.522 ms
8 brvwil1wcx3-pos2-0-oc192.wcg.net (64.200.240.122) 51.194 ms 51.895
ms 51.238 ms
9 chcgil9lch1-pos7-1.wcg.net (64.200.210.118) 51.855 ms 51.628 ms
52.393 ms
10 * sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 3.730 ms 3.657 ms
11 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 4.464 ms 3.651 ms
4.180 ms
12 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 4.019 ms 3.637 ms
3.559 ms
13 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 4.268 ms 3.775 ms
4.433 ms
14 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 4.150 ms 4.602 ms
4.055 ms
15 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 4.896 ms 4.502 ms
4.058 ms
16 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 4.767 ms 4.119 ms
4.283 ms
17 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 4.650 ms 4.882 ms
4.686 ms
18 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 4.664 ms 4.553 ms
4.685 ms
19 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 5.402 ms 4.969 ms
4.558 ms
20 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 5.013 ms 4.907 ms
4.561 ms
21 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 5.151 ms 5.162 ms
5.311 ms
22 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 5.151 ms 5.039 ms
5.561 ms
23 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 5.527 ms 5.166 ms
5.408 ms
24 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 5.523 ms
sntcca1wcx2-pos11-0.wcg.net (64.200.240.221) 2.880 ms !H *
25 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 5.978 ms 5.568 ms
5.801 ms
26 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 5.768 ms 6.237 ms
5.554 ms
27 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 6.407 ms 5.779 ms
6.180 ms
28 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 5.641 ms 5.764 ms
6.057 ms
29 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 6.017 ms 6.401 ms
6.305 ms
30 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 6.268 ms 6.029 ms
6.054 ms
31 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 6.398 ms 6.623 ms
6.660 ms
32 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 6.524 ms 6.526 ms
6.559 ms
33 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 6.773 ms 7.032 ms
6.682 ms
34 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 6.525 ms 6.778 ms
6.808 ms
35 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 7.023 ms 7.284 ms
7.061 ms
36 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 7.149 ms 7.035 ms
7.309 ms
37 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 7.516 ms 7.519 ms
7.554 ms
38 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 7.266 ms 7.274 ms
7.180 ms
39 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 7.892 ms 7.648 ms
7.680 ms
40 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 8.022 ms 7.902 ms
7.933 ms
41 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 8.272 ms 8.413 ms
8.182 ms
42 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 8.148 ms 7.882 ms
8.049 ms
43 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 8.771 ms 8.393 ms
8.183 ms
44 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 8.392 ms 8.511 ms
8.681 ms
45 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 8.399 ms 8.531 ms
8.818 ms
46 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 8.444 ms 8.188 ms
8.676 ms
47 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 8.891 ms 8.764 ms
8.917 ms
48 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 8.639 ms 9.002 ms
8.553 ms
49 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 9.267 ms 9.003 ms
9.675 ms
50 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 8.762 ms 9.012 ms
9.060 ms
51 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 9.499 ms 9.114 ms
9.434 ms
52 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 9.880 ms 9.225 ms
9.524 ms
53 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 9.764 ms 9.385 ms
9.677 ms
54 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 9.890 ms 9.524 ms
10.051 ms
55 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 10.263 ms 10.150 ms
9.928 ms
56 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 9.765 ms 9.519 ms
9.926 ms
57 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 10.390 ms 10.271 ms
10.177 ms
58 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 10.390 ms 10.239 ms
10.426 ms
59 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 10.514 ms 10.889 ms
10.552 ms
60 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 10.658 ms 10.464 ms
10.508 ms
61 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 10.748 ms 10.836 ms
10.923 ms
62 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 10.891 ms 10.752 ms
10.926 ms
63 sntcca2lch1-pos7-1.wcg.net (64.200.149.14) 10.889 ms 11.397 ms
10.917 ms
64 sntcca1wcx2-pos0-0.wcg.net (64.200.149.13) 10.999 ms 10.749 ms
10.925 ms
They have had this several times now in the last 6 months.
|
| Posted by maxcjho, 11-01-2004, 02:48 PM | |
My site is up.
|
| Posted by The Neoracle, 11-01-2004, 02:48 PM | |
How should I send the email, through my VPS that's down? Or?
|
| Posted by bear, 11-01-2004, 02:48 PM | |
Yup, back now. Fast work Servint.
|
| Posted by HSRGeorge, 11-01-2004, 02:49 PM | |
And its back. I had about 17 mins downtime...
|
| Posted by brazosit, 11-01-2004, 02:49 PM | |
My server is now back up!
|
| Posted by mkc, 11-01-2004, 02:49 PM | |
Back up for me.
|
| Posted by blueface, 11-01-2004, 02:49 PM | |
Seems back up now. So any explanation what was going on?
|
| Posted by roccol, 11-01-2004, 02:50 PM | |
back up as well.
|
| Posted by sirius, 11-01-2004, 02:53 PM | |
This isn't their support forum. They have provided their contact information (Toll Free number along with e-mail), maybe contact them and find out?
Sirius
|
| Posted by rmeden, 11-01-2004, 02:55 PM | |
I'm back too... about 20 minutes down.
99.9% up means 525 minutes down a year... anyone counting?
No annoucement in the support forum yet (6min) ... the slackers.
Robert
(still happy at servint)
|
| Posted by deborahsmith, 11-01-2004, 02:56 PM | |
I want to hear more about this WilTel, Inogenius?
Can you enlighten me?
|
| Posted by box0p, 11-01-2004, 03:01 PM | |
Gnaps we forgive you!
Ever since i heard Gnaps was getting replaced by another provider i asked myself why? I still do not understand why Servint decided to part with them and replace them with BTN. Good business decission? We will see! Lets see the mix of other providers sooner than later, as it seems BTN is nothing like as good as gnaps.
-Boxop
Last edited by box0p; 11-01-2004 at 03:08 PM.
|
| Posted by blueface, 11-01-2004, 03:12 PM | |
box0p, BTN is a great network and I don't like you to blame them. I know for sure the problem was not with BTN cause I was able to access BTN network from my other servers during the ServInt outage.
Something is going wrong with ServInt network and unless they upgrade their network, we'll see more outages like this. Did anyone notice a high packet loss for half an hour last night?
|
| Posted by box0p, 11-01-2004, 03:15 PM | |
Been with Servint quiet sometime and i loved the old gnaps network, just a personal thing. BTN seems to be just like any other provider good in a mix and blend of providers. Either way something needs looked into. As its not the same as it used to be.
-Boxop
|
| Posted by Joshua, 11-01-2004, 04:07 PM | |
I can't figure out why a provider who bills themselves as a high-end provider would only rely on one connection, and why it would be BTN, at that (as their routes in the US and Canada aren't the best - They're amazing for overseas, though). I don't even know if a BTN issue was the cause of the downtime, but I just don't trust single-homed bandwidth.
|
| Posted by HSRGeorge, 11-01-2004, 04:12 PM | |
BTN was not this time and has never been AFAICT/K the cause of any downtime.
|
| Posted by kmsd, 11-01-2004, 04:39 PM | |
You should keep an off-network email address on file with the NOC and use it to communicate with them.
|
| Posted by s.h.a.zz.y, 11-01-2004, 05:49 PM | |
You are assuming they have one provider?
..from what I can tell they take peering to, so they are technically not single homed.
|
| Posted by HSRGeorge, 11-01-2004, 05:52 PM | |
Among (many, many) others BTN connects with UUNet and Sprint...
|
| Posted by s.h.a.zz.y, 11-01-2004, 05:54 PM | |
If this was in reply to my post, I was referring to Servint not being single-homed. I am aware of the BTN network.
|
| Posted by TomK, 11-01-2004, 06:43 PM | |
They are (ServInt), after removing the GNAPs, I think Reed even posted in his dedicated sales thread about having just BTN.
|
| Posted by KarlZimmer, 11-01-2004, 07:19 PM | |
Wow, ServInt is single-homed, I never realized that... I'm honestly amazed that such a company would take the risk of being single-homed. Not a fan of that business practice. So many reasons to be multi-homed...
|
| Posted by FHDave, 11-01-2004, 07:50 PM | |
If their SLA is covering you on a yearly basis, not monthly basis, then I will find it very unsual. You should be covered with an SLA that's being applied on a monthly basis. If they are down for more than 43 minutes a month (for 99.9% uptime), then you should receive compensation. That's the norm in the industry.
|
| Posted by NeonHQ, 11-01-2004, 08:24 PM | |
Thanks. now i know it is not my end.
Anyway, it is up and running
|
| Posted by blueface, 11-02-2004, 02:30 AM | |
Yeah Karl, sad but true. That's also what I'm concerned about. ServInt network was quite solid with GNAPS, but now it seems to suffer outages and high packet loss quite often.
|
|
 Add to Favourites
 Print this Article
|
