| ASN |
AS402801 — ARIN, Org ANDRI-4 (Andrii Co.) |
| PREFIXES |
2602:f337:ed::/48 — enodia, Seattle. Live.
2602:f337:a5::/48 — triton, Amsterdam. Live.
2602:f337:ac::/48 — anycast service prefix. Live, announced from Amsterdam alone today; Seattle joins it later, and the AS-path is the only thing that will change.
IPv6 only; no IPv4 is originated. All three carry an exact-length ROA and sit in the AS-SET below. |
| ALLOCATION |
2602:f337::/40 (ARIN direct allocation, NET6-2602-F337-1) |
| RPKI |
One exact-length ROA per /48 — maxLength equal to the prefix length, origin AS402801. All three validate Valid. No ROA covers the /40 itself, deliberately: a covering ROA would either invalidate our /48s or authorise a forged-origin hijack of the /48s we do not announce. Each future /48 gets its own ROA before it is announced. Please drop RPKI-Invalid routes. |
| IRR |
AS-SET ARIN::AS-ANDRII — build IPv6 filters from this, not from the bare ASN. The object is in the ARIN IRR (source: ARIN, mirrored by RADb and NTT) alongside aut-num AS402801 and one exact-match route6 per announced /48 (auto-managed from the ROA). The set lists only AS402801 — we have no customer cone. |
| PREFIX FILTER |
bgpq4 -6 -S ARIN AS-ANDRII — emits the three /48s above as exact-match entries. Use -6: we originate no IPv4, so without it bgpq4 returns an empty list. Same result as bgpq4 -6 AS402801 while the set has one member. |
| SUGGESTED MAX-PREFIX |
IPv6: 10 · IPv4: 0 |
| TRANSIT |
Seattle — AS20473 (Vultr). AS-path … 20473 402801.
Amsterdam — AS34927 (iFog) and AS209022 (Tschajera).
The aut-num carries the policy for all five neighbours. |
| IX PRESENCE |
FogIXP EU — 2001:7f8:ca:1:0:40:2801:1, route servers AS47498
FogIXP Amsterdam — 2001:7f8:16c:1:0:40:2801:1, route servers AS61190
We are on both route servers. Bilateral sessions on either LAN are welcome — mail peering@andrii.co. |
| LOCATION |
Seattle, Washington, US · Amsterdam, NL |
| GEOFEED |
/.well-known/geofeed — RFC 8805, Medina WA |
| INBOUND POLICY |
We accept no routes. Every session runs import none. AS402801 is a stub: it originates its own prefixes and buys transit for everything outbound, so please do not expect us to carry yours. |
| OUTBOUND POLICY |
Our own prefixes only, originated from a static filter and capped at 10 routes per session in block mode. We provide transit to no one, and our AS-SET has no customer cone. |
COMMUNITIES, MED,
DAMPING |
On every peering and transit session we set no BGP communities and act on none; the only communities we touch are the blackholing ones in the next row. We set no MED and act on none. We apply no route damping. If you need an announcement prepended or scoped, ask and we will set your own communities toward the route servers. |
| BLACKHOLING |
We take part in Team Cymru’s UTRS (AS64496), the community remote-triggered-blackhole feed. Under a volumetric flood we may announce a /128 inside one of our own /48s to UTRS, tagged BLACKHOLE (65535:666, RFC 7999) plus NO_EXPORT, asking participants to discard traffic to that one address of ours; in return we install other participants’ 64496:0 requests as discard routes at our own edge. These routes stay out of band: nothing learned from UTRS is re-announced, and our sessions with you keep importing nothing. We may later signal the same request with BLACKHOLE toward an upstream or route server that honours it, or add UTRS flowspec; this page will say so first. |
| PEERING POLICY |
Open — settlement-free, no NDA, no contract, no traffic minimum. We are on both FogIXP route servers above; a bilateral session is a mail away. |
| PEERINGDB |
peeringdb.com/net/43052 |
| MANRS |
We build this network to the MANRS actions for network operators, and we ask the same of our peers: filter what you announce, keep IRR and RPKI records that match it, publish a NOC contact that answers, and stop spoofed source addresses at your own edge. |