Peering Policy

Armstrong Utilities, Inc. is an Internet service provider offering services in Pennsylvania, Ohio, Kentucky, West Virginia, Maryland and New York to residential and business customers via fiber and HFC.

Current information is available from PeeringDB - https://as27364.peeringdb.com

Armstrong Utilities, Inc. primary ASN is 27364
IRR AS-set object AS27364:AS-ALL
IPv4 Prefixes 300
IPv6 Prefixes 150

Armstrong Utilities, Inc. peers with IX provided route servers where they are available.
Armstrong Utilities, Inc. preference to peer directly with any network with more than 10 Gbps in the dominant direction rather than via the IX route server.
Armstrong Utilities, Inc.’s preference is to establish private peering with any network with more than 50 Gbps in the dominant direction rather than peering via an IX fabric.

Armstrong Utilities, Inc. supports 100GE peering connections.
Armstrong Utilities, Inc. prefers 100G-LR4 optics for peering.

Armstrong Utilities, Inc. has a selective peering policy. Anyone wishing to peer with Armstrong Utilities, Inc. at a common location should contact peering@agoc.com. For peering to be mutually beneficial, please confirm that the following requirements are met before requesting a peering connection.

Requirements

Peering partners are expected to:

• Peer with a globally unique ASN assigned by an RIR.
• Maintain up-to-date network and contact information in peeringDB.
• Maintain an IRR as-set one of the IRR databases mirrored by RADb.
• Maintain IRR route/route6 objects for all announced prefixes.
• Operate a 24x7x365 NOC that will promptly work to resolve any reports of trouble with a peering connection. In this context “trouble” includes but is not limited to – route flaps, max prefix violations, excess traffic, interface flaps, abuse, and security incidents.
• Only announce prefixes allocated or assigned by an RIR to the announcing ASN or prefixes delegated to an immediate customer ASN.
• Only route traffic destined to prefixes advertised by Armstrong Utilities, Inc. via peering connections. In particular, the following are violations of this requirement:
• Sourcing traffic from a prefix not announced to Armstrong Utilities, Inc. via the peering connection.
• Sending traffic destined to a prefix not announced by Armstrong Utilities, Inc. over the peering connection.
• Resetting next hop.
• Monitor capacity between the networks and augment before congestion occurs.

It is recommended, but not required for peering partners to:

• Peer with Armstrong Utilities, Inc. at more than one location.
• Maintain ROAs for all announcements.
• Provide a looking glass or route server.

Armstrong Utilities, Inc. routing policy prefers routes learned via private peering (PNI) over those learned via public peering (IX).

Armstrong Utilities, Inc. announces all the routes in the AS27364:AS-ALL as-set at all peering locations but under certain circumstances may announce a subset.

Armstrong Utilities, Inc. does not recommend the use of MD5 but can support it.

Armstrong Utilities, Inc. reserves the right to terminate peering sessions at any time for any reason. Under normal circumstances Armstrong Utilities, Inc. will provide 30-day notification before terminating a peering session but reserves the right to immediately terminate a peering session to protect the integrity of the Armstrong Utilities, Inc. network.

Armstrong Utilities, Inc. reserves the right to modify this policy as needed.