My enterprise hosts a few externally reachable services, but not very many of them. Currently we have a provider assigned /29 on our circuit, and publish dns records for them.
The problem is our carrier is a single point of failure. We want to bring in a second carrier in the interest of redundancy and failover.
But the standard way of doing this seems to be to acquire our own ASN, and our own block of public IP space, and that we need a /23 minimum. (The reason I say /23 is so we could advertise a specific /24 to one carrier and the whole /23 to the other for clean failover.)
We only host a small handful of services, so a /29 is just right for us, a /23 is massive overkill. Even a /24 is massive overkill.
It also sounds incredibly burdensome for an org our size to maintain all the records with Arin of having our own ASN, and own IP space, etc.
Is there any service or method out there for accomplishing carrier failover without needing to advertise carrier-independent nets out to multiple carriers? How do smaller orgs like ours handle this? Do they just accept the single point of failure and move on with life?
No comments:
Post a Comment