On Wed, Jun 11, 2014 at 1:28 AM, Saku Ytti wrote:
> On (2014-06-10 12:39 -0500), Blake Hudson wrote:
> There is nothing to summarize away from global BGP table, if you have number
> showing less, it's probably counter bug or misinterpretation.
> Global BGP table, single BGP feed, will take same am
Matthew Petach wrote the following on 6/10/2014 7:03 PM:
On the couple Cisco platforms I have available with full tables, Cisco
summarizes BGP by default. Since this thread is talking about Cisco
gear, I think it's more topical than results from BIRD.
One example from a non-transit AS:
On 10/06/14 12:28, Bjoern A. Zeeb wrote:
> You mean it’s more likely people acquire/merge with other companies for IP
> space then go through transfer? https://www.arin.net/knowledge/statistics/
You have to consider that most likely there will be an increase in
de-aggregation due to:
- The RIR
Dear colleagues,
Please find the CFP for RIPE 69 in London below.
The deadline for submissions is 31 August 2014.
Please also note that speakers do not receive any extra reduction or
funding towards the meeting fee at the RIPE Meetings.
Kind regards
Filiz Yilmaz
RIPE PC Chair
http://www.ripe.n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cisco IOS XR Software IPv6 Malformed Packet Denial of Service Vulnerability
Advisory ID: cisco-sa-20140611-ipv6
Revision 1.0
For Public Release 2014 June 11 16:00 UTC (GMT)
Summary
===
A vulnerability in the parsing of malformed Internet
Folks -
As noted in a prior message to the "nanog" mailing list, it is quite likely
that some of the address blocks listed in this CIDR report under the heading
"Possible Bogus Routes" will shortly be issued to requesters. In the case of
unassigned blocks in the ARIN free pool, this is ex
Looks like they've finally completely blocked off their abuse mailboxes.
- The following addresses had permanent fatal errors -
(reason: 554 Message not allowed - [298])
- Transcript of session follows -
... while talking to mx-eu.mail.am0.yahoodns.net.:
DATA
<<< 554
goe...@anime.net wrote the following on 6/11/2014 3:00 PM:
Looks like they've finally completely blocked off their abuse mailboxes.
- The following addresses had permanent fatal errors -
(reason: 554 Message not allowed - [298])
- Transcript of session follows -
...
It's the content.
They're spamfiltering their abuse mailbox.
-Dan
On Wed, 11 Jun 2014, Blake Hudson wrote:
goe...@anime.net wrote the following on 6/11/2014 3:00 PM:
Looks like they've finally completely blocked off their abuse mailboxes.
- The following addresses had permanent fata
On 11 June 2014 16:41, wrote:
> It's the content.
>
> They're spamfiltering their abuse mailbox.
>
As supporting evidence I offer the fact that this entire conversation ended
up in my (Google) Junk folder.
--
Harald
RoJlx100
--
Jason Hellenthal
Voice: 95.30.17.6/616
JJH48-ARIN
> On Jun 11, 2014, at 17:28, Harald Koch wrote:
>
>> On 11 June 2014 16:41, wrote:
>>
>> It's the content.
>>
>> They're spamfiltering their abuse mailbox.
>
>
> As supporting evidence I offer the fact that this entire conve
Im wondering if anyone else is seeing strangeness.
|--|
| WinMTR statistics
|
| Host - % | Sent | Recv | Best |
Avrg |
I have no issues reaching AKAMAI(weather.gov)
- jared
On Jun 11, 2014, at 10:52 PM, Bryan Tong wrote:
> Im wondering if anyone else is seeing strangeness.
>
> |--|
> | W
I also can't reach weather.gov.
traceroute to weather.gov (204.227.127.201), 64 hops max, 72 byte packets
1 192.168.124.1 (192.168.124.1) 0.315 ms 0.140 ms 0.134 ms
2 ge-2-2-0-32767-sur01.michiganave.dc.bad.comcast.net
(50.202.87.153) 0.383 ms 0.359 ms 0.339 ms
3 ae-19-0-ar04.whitema
AS32878 appears to have disappeared.
On Wed, Jun 11, 2014 at 8:05 PM, Will Dean wrote:
> I also can't reach weather.gov.
>
> traceroute to weather.gov (204.227.127.201), 64 hops max, 72 byte packets
> 1 192.168.124.1 (192.168.124.1) 0.315 ms 0.140 ms 0.134 ms
> 2 ge-2-2-0-32767-sur01.mic
No luck from here.
weather.gov resolves as 204.227.127.201 for me, and I have no routes for that
IP.
However, www.weather.gov is a CNAME for www.weather.gov.edgesuite.net. which
in turn is canonical for a895.g.akamai.net. for me. That resolves to
216.23.154.72 & 216.23.154.75, which heads
On Thu, Jun 12, 2014 at 2:52 AM, Bryan Tong wrote:
> Im wondering if anyone else is seeing strangeness.
I have no trouble accessing www.weather.gov.
(akamai CDM based). weather.gov, on the other hand,
seems inaccessible (noaa.gov supported).
On 6/11/2014 11:13 PM, Hugo Slabbert wrote:
> No luck from here.
>
> weather.gov resolves as 204.227.127.201 for me, and I have no routes
> for that IP.
Likewise here, and we have various views.
> UTC-Border#show ip route 204.227.127.201
> % Network not in table
BGP path falls back to default ro
Is anyone else noticing a lot of problems with Amazon S3 US Standard
problems.We're seeing a lot of customer complaints of connects then
hangs/timesout mid transfer...
Mostly coming from connections originating in the NYC area or from europe
passing through nyc on it's way.
Bryan Socha
Networ
Also the main forecast.weather.gov seems to be okay.
$ ping forecast.weather.gov
PING a1380.g.akamai.net (64.208.159.26): 56 data bytes
64 bytes from 64.208.159.26: icmp_seq=0 ttl=50 time=1009 ms
64 bytes from 64.208.159.26: icmp_seq=1 ttl=50 time=100 ms
64 bytes from 64.208.159.26: icmp_seq=2 ttl
On Thursday, June 12, 2014 05:17:37 AM Gary Buhrmaster
wrote:
> I have no trouble accessing www.weather.gov.
> (akamai CDM based). weather.gov, on the other hand,
> seems inaccessible (noaa.gov supported).
Same thing here from Africa.
Mark.
signature.asc
Description: This is a digitally sign
Can someone from aws contact me off list. we think we found where the
issue might be.
Thanks,
Bryan Socha
Network Engineer
DigitalOcean
On Thu, Jun 12, 2014 at 12:16 AM, Bryan Socha
wrote:
> Is anyone else noticing a lot of problems with Amazon S3 US Standard
> problems.We're seeing a
22 matches
Mail list logo
