It exists but not in bgp form - http://www.spamhaus.org/drop/
Dont Route Or Peer
srs
I have a customer that sells online, and is dropping stuff from ec2 today due to abuse.
Andy
Patrick W. Gilmore wrote:
At the end of the day, nobody is going to drop packets for amazon's IP space.
I'm afraid reality disagrees with you - there already are networks doing it.
Being big does not guarantee you ability to do Bad Things.I didn't imply that it did.
Actually, that is exactly what you did.
But the ability to block without causing significant collateral damage becomes more and more difficult as IPs become less tied to the organization using them.
True (and rather obvious). Here's another obviously true statement: As more & more spam comes from a set of IP addresses, it becomes less & less likely you should accept e-mail from that space.
That said, you're right that people are doing it now. Consensus from friends running their apps on EC2 is that you can't expect to be able to send any email from EC2 and hope for a high deliverability rate.
Not news to anyone who works on anti-spam or e-mail deliverability. Perhaps the collateral damage will force Amazon to get things fixed faster.
Or maybe not, but either way I don't see how you can blame someone for not wanting to accept e-mail from EC2.
Hi folks...
We're working on some plans to peer in the Seattle area. Choices so far
considered are SIX and PAIX Seattle pretty much....
I was of the impression that if you get a port on one of these
exchanges, you can connect to the other one as well? Just looking for
clarification from folks who are connected out there..
Any charges to
go between the exchanges or it just included?
Thanks,
Paul
Hello Paul:
Hi folks...
We're working on some plans to peer in the Seattle area. Choices so far
considered are SIX and PAIX Seattle pretty much....I was of the impression that if you get a port on one of these
exchanges, you can connect to the other one as well? Just looking for
clarification from folks who are connected out there..Any charges to
go between the exchanges or it just included?
Speaking from the SIX side, there is no charge to connect to the fabric if
you supply the optics, and there is a one-time fiber cross connect charge of
$200.00 US. The SIX and PAIX are directly connected and you can peer across
the fabric. The SIX page is http://www.seattleix.net for more info or you
can email me directly.
I have no idea about charges related to PAIX.
Mike
SIX Tech Guy Hat On
Hmmm Seems Pacific bit the bullett around 2:25 est all annoucements were
dropped.
http://cidr-report.org/cgi-bin/as-report?as=AS27595&v=4&view=2.0
I would ask for comment by Intercage staff but they don't have email. Emil
is unresponsive via phone,
James
And keep in mind that while the SIX and PAIX-SEA are directly connected,
the exchanges are on different VLANs from the perspective of a PAIX-SEA
connection.
If you connect on the SIX side, you can only reach the SIX fabric. No
MRC.
If you connect on the PAIX-SEA side, you can reach both the SIX fabric and
the PAIX-SEA fabric via a single router port. For MRC talk to an S&D rep.
Chris
Thanks very much... we have a price from S&D for the x-connect. If we
connect on the PAIX side (most likely) do we need multiple VLAN's? I
had planned on a single VLAN on the port for there - just need to
understand
Thanks,
Paul
If you are in S&D/PAIX's facility, you have two options for connecting to
the SIX:
- direct to the SIX core via the fiber-meet-me-room, thus no VLAN. You
won't get access to the PAIX-SEA fabric with this method, but if what
you really want is the SIX, this is the way to go.
- direct to the PAIX-SEA switch, in which case you'll need to instruct
S&D to enable your port to also have access to the SIX fabric. Your
router will have two VLAN interfaces on the port, one for PAIX-SEA and
one for the SIX.
Feel free to direct further questions to info@seattleix.net if you like.
Chris