18 May
2012
18 May
'12
10:55 a.m.
Hi,
For around the last hour there have been intermittent periods of
high packet loss. I'm working with our transit provider on this at
the moment and will give you more information when I have it.
Apologies for the disruption.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
18 May
18 May
12:13 p.m.
Hello,
On Fri, May 18, 2012 at 10:55:58AM +0000, Andy Smith wrote:
For around the last hour there have been intermittent
periods of
high packet loss. I'm working with our transit provider on this at
the moment and will give you more information when I have it.
The issues were caused by a problem with one of our transit
provider's (Jump Networks) LINX ports. At approximately 11:00Z the
port was shut down causing traffic to use a different port, which
worked around the problem.
Apologies again for the disruption.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
19 May
19 May
1:59 p.m.
On 18 May 2012, at 13:13, Andy Smith wrote:
Hello,
On Fri, May 18, 2012 at 10:55:58AM +0000, Andy Smith wrote:
Hi Andy,
I'm still having issues reaching a rackspace/slicehost vm, and seem to match this
timing suspiciously well (notifications fell silent yesterday morning, and have remained
so)
$ ping -c 1 prowlapp.com
PING prowlapp.com (209.20.72.170) 56(84) bytes of data.
From jump-gw-4.lon.bitfolk.com (212.13.194.4) icmp_seq=1 Destination Host Unreachable
I can reach it from home, from a third network, and traceroutes end convincingly within
rackspace's network (the endpoint is a slicehost vm within rackspace's network)
But from my bitfolk vps, this address (and random stabs in the dark at .72.1, .71.1 and
.70.1) are coming back unreachable before they leave the jump gateways.
Any ideas?
Thanks,
Shaun
For around the last hour there have been
intermittent periods of
high packet loss. I'm working with our transit provider on this at
the moment and will give you more information when I have it.
The issues were caused by a problem with one of our transit
provider's (Jump Networks) LINX ports. At approximately 11:00Z the
port was shut down causing traffic to use a different port, which
worked around the problem.
Apologies again for the disruption.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
10:06 p.m.
Hi Shaun,
On Sat, May 19, 2012 at 02:59:45PM +0100, Shaun ONeil wrote:
I'm still having issues reaching a
rackspace/slicehost vm, and seem to match this timing suspiciously well (notifications
fell silent yesterday morning, and have remained so)
$ ping -c 1 prowlapp.com
PING prowlapp.com (209.20.72.170) 56(84) bytes of data.
From jump-gw-4.lon.bitfolk.com (212.13.194.4) icmp_seq=1 Destination Host Unreachable
This was unrelated to yesterday's problem.
It seems that Rackspace deaggregated their /19 into thirty one /24s:
http://www.ris.ripe.net/dashboard/209.20.64.0/19
and Jump does not accept /24 announcements. I've got them to put an
exception in and have asked Rackspace to put a covering route, so it
works now.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
20 May
20 May
8:45 a.m.
This was unrelated to yesterday's problem.
It seems that Rackspace deaggregated their /19 into thirty one /24s:
http://www.ris.ripe.net/dashboard/209.20.64.0/19
and Jump does not accept /24 announcements. I've got them to put an
exception in and have asked Rackspace to put a covering route, so it
works now.
They do if that was the size of the allocation, the problem is with
deaggregation, not the size of the announcement, iirc
4598
days inactive
4600
days old
4 comments
3 participants
participants (3)
-
Andy Smith -
Philip Veale -
Shaun ONeil