Peering

Peering Information

You can find more information about our network on PeeringDB.

Misaka.io (AS917, AS57695) has a generally open peering policy. We welcome all peers in all locations where we are present.

Peers should meet the following criteria:

All peers must maintain a 24×7 contactable NOC.
Peers are encouraged to provide access to a Looking Glass and join the NLNOG RING or RIPE Atlas to facilitate troubleshooting.
Peers should not point a gateway of last resort or default route directed towards our session. We may blackhole your MAC address without prior notice if you do so.
MD5 use is discouraged but can be configured if required.
We reserve the right to suspend peering for an indefinite period of time for any kind of abuse, DDoS, etc.
Remote peering is discouraged but can be discussed on a case-by-case basis.

Peers must establish BGP sessions with all neighbors and enable multiple routing when multiple connections exist.

Both parties agree to review the capacity on a regular basis and to increase it as required.
The peer should use reasonable endeavours to provide us with advance notice of any planned maintenance work that will affect the PNI circuits.

See PeeringDB for more information on our IX information.

You can find more information about our network on PeeringDB.

Misaka.io (AS917, AS57695) has a generally open peering policy. We welcome all peers in all locations where we are present.

Peers should meet the following criteria:

All peers must maintain a 24×7 contactable NOC.
Peers are encouraged to provide access to a Looking Glass and join the NLNOG RING or RIPE Atlas to facilitate troubleshooting.
Peers should not point a gateway of last resort or default route directed towards our session. We may blackhole your MAC address without prior notice if you do so.
MD5 use is discouraged but can be configured if required.
We reserve the right to suspend peering for an indefinite period of time for any kind of abuse, DDoS, etc.
Remote peering is discouraged but can be discussed on a case-by-case basis.

Peers must establish BGP sessions with all neighbors and enable multiple routing when multiple connections exist.

Both parties agree to review the capacity on a regular basis and to increase it as required.
The peer should use reasonable endeavours to provide us with advance notice of any planned maintenance work that will affect the PNI circuits.

See PeeringDB for more information on our IX information.