Unitas Global - AS1828 - Network Information
Unitas Global operates a worldwide transport and IP transit network in support of its mission to improve network connectivity performance for its enterprise customers. We believe strongly in the ability for well-designed and implemented peering to improve our customer experience while using network-connected services.
Tools and Links
Peering requests should be sent to Unitas Global via email to email@example.com. Members of our peering team are normally available Monday to Friday 0200-2200 UTC, and we will endeavour to review requests within 48 hours. Requests for peering with AS1828 are reviewed according to our policy below, which serves as a general guideline, however Unitas Global reserves the right to accept or reject requests at its sole discretion.
General Technical Requirements
- A publicly routable and visible unique ASN.
- 24x7x365 Network Operations Center (NOC), where problems can be reported.
- Full and correctly- updated PeeringDB entry and profile. Our provisioning systems rely on this for prefix lists and limits.
- Peer networks must only advertise their own internal and customer routes (no transit routes), and will not include routes with a private ASN in the advertisement.
- Generally peers should advertise consistent routes at all common peering points. Exceptions are made for content delivery networks and cloud services. (Please note in requests if this is a requirement.)
- Where possible we prefer to have direct sessions at multiple internet exchanges as we do not necessarily advertise all of our routes to IX route servers.
- Advertised routes shall all be registered in an appropriate IRR, and where possible will have RPKI Valid ROAs for each advertised route. Unitas Global reserves the right to reject RPKI Invalid routes received from peers.
- MD5 authentication on peering sessions is not required, nor recommended, but can be supported if required.
- Unitas Global will not normally peer with an ASN that shows up in our current AS-SET (i.e. a Customer, or a downstream of that Customer). If you believe your request has been rejected because of this restriction, please contact us.
- Unitas Global will not normally peer with a downstream customer of an existing peer.
- Please ensure you follow our Maximum prefix limits as detailed in our PeeringDB record (https://as1828.peeringdb.com)
Public Internet Exchanges (IXPs)
- At this time, there are no minimum traffic requirements for establishing bilateral BGP sessions over public internet exchanges, however Unitas Global generally looks for some meaningful level of traffic or customer benefit before establishing new sessions.
- Sessions between Unitas Global and a peer network must exist in all common service regions/markets to avoid possible "trombone" routes that degrade performance. Unitas will not peer with networks that don't have common peering points in all shared markets and IXs.
- Unitas Global peers with many IX route servers; in some cases only advertising regionally-originated routes.
- Requests for bilateral sessions in public exchanges will be considered on an individual case basis, and will receive our full customer routing table.
Private Interconnects (PNIs)
- Generally the same requirements apply for public exchange sessions, in addition to the following requirements:
- We expect an aggregate of no less than 5 Gbps of traffic for peer networks requesting PNIs.
- PNIs should be established in all common service areas. Unitas generally discourages mixing public IX sessions with PNIs.
- PNI cross connect costs will be shared equally by both networks.
- PNI links are supported via 10G or 100G single mode fiber links, generally configured as LACP-active LAGs.
- We expect peers to utilize closest-exit routing; Unitas does the same.
- Requests to honor MEDs will be reviewed on an individual case basis. (Please note in requests if this is a requirement.)
- If newly-requested sessions are not established within 14 days of deployment, sessions will be automatically removed.
- Sessions idle for more than 14 days without a previously-declared extended maintenance will be automatically removed.
- Unitas Global reserves the right to suspend or terminate peering at any time, although we will always attempt to work with our peering partners to remediate any issues.
- Each party will bear its own expenses related to establishment of peering. (Cross connects, IX ports, necessary licenses or other regulatory approvals.)
- None of the above policies, or the act of peering with Unitas Global create any binding obligations or performance guarantees by Unitas Global.
- While we aim to keep bandwidth usage under 80% of capacity on any particular link and we expect the same of our peers, this cannot be guaranteed.