# The network: AS402801, from Seattle - **Source:** https://andrii.cloud/network/ - **Title:** AS402801 — BGP, BYOIP and IPv6 from Seattle — Andrii Cloud > AS402801 announces its own IPv6 /48s from Seattle out of an ARIN /40 allocation. Bring your ASN and your prefixes: a BGP session on every shape, filtered against IRR and RPKI. > The colocation is being built. The network already runs — `AS402801`, its own address space, its own routing policy, and a BGP session for anybody who brings an ASN. This page says exactly what that is today, and exactly what it is not. **Before you read any further** — This is a pre-launch interest register. Nothing here is a quote, no capacity is reserved, and no service is being sold today. ## Seattle-homed, and what that means precisely `AS402801` announces its own IPv6 /48s from Seattle out of an ARIN /40 allocation, over transit from `AS20473`, plus Team Cymru UTRS blackhole sessions. It does not originate the /40, and it has one transit upstream in Seattle today. The same ASN has been running BGP on two continents for a while now, which is the part of this that is not a plan: the routing policy, the IRR objects, the RPKI ROAs and the operational habit all exist and can be checked by anybody, from outside, without asking us. We also operate a node in Amsterdam for our own network — monitoring and anycast — and we do not sell EU-based hosting today. _Planned, not present tense: the routing design for the Westin assumes a second transit upstream and a path to the exchange, so that a Seattle failure has somewhere to go. Neither exists today, and this sentence is the only place on this site that says otherwise about the future._ ## Bring your ASN, bring your prefixes BYOIP at no additional charge — the one thing on this list that almost nobody in Seattle puts in writing. - A BGP session to your ASN on any colocation shape, and on a virtual machine too - Your prefixes announced under your own origin, not ours, with a letter of authorisation - Filtering built from IRR objects and RPKI ROAs — RPKI-invalid announcements are dropped, not accepted and noted - Full table, or a default, or both — your session, your choice - Standard communities for blackholing and for controlling where your routes go - A hijacked announcement is an immediate suspension, and we will tell you why before we tell anybody else _If you do not have an ASN yet, that is a conversation rather than a blocker — it is the single most common question we get, and we will tell you what to file and with which registry._ ## IPv6 first, IPv4 honest A /48 with every service. Not on request, not on a form, not a /56 that turns into a /48 when you complain — the allocation this network holds is large enough that being careful with it would be theatre. IPv4 is the opposite, and we would rather say so than pretend. The ARIN IPv4 /24 waitlist runs about 9–14 months, which is why IPv4 is metered and IPv6 is not. Addresses beyond the one in your shape are leased, announced and geolocated to Seattle, and they are billed as the scarce thing they are. ## The abuse baseline, and what it is sized for Cloudflare's H1 2026 DDoS threat report puts 96.6% of attacks under 500 Mbps and 90.6% of them over within ten minutes. Those are their figures about the internet, not ours about our network — and they are the reason our planned baseline is flow detection with remote-triggered blackholing rather than an always-on scrubbing contract nobody's traffic profile justifies. The baseline is included in every shape and it is a baseline: it drops the attack, which sometimes means dropping the target with it. A customer whose traffic has to stay clean **during** an attack — a game server, a streaming service, a public-facing portal — needs the scrubbed-transit line instead, and that line activates when enough customers commit to it rather than when a marketing page says it exists. ## Do not take our word for any of this Everything above about `AS402801` is in public registries, and none of it is ours to edit on your behalf. The routing policy, the peers, the prefixes and their RPKI status are at [PeeringDB](https://www.peeringdb.com/asn/402801), [bgp.tools](https://bgp.tools/as/402801) and [Hurricane Electric's BGP toolkit](https://bgp.he.net/AS402801). If a sentence on this page disagrees with one of those three, the registry is right and we owe you a correction. What we do not have is a status page or a looking glass. Both are on the list, and neither is linked here, because a link to a status page that does not exist is worse than no status page at all. ## Bringing a network with you? Tell us the ASN, the prefixes and roughly what the traffic looks like. If the answer is that we cannot take it yet, you will get that answer instead of a sales call. _Everything on this page describes a service we intend to offer. It is not a binding offer capable of acceptance, no capacity is reserved, nothing here is a quote, and specifications will change. Our [Terms](/terms/) explain what this page is and is not._ ## Other pages on this site (Markdown) - [/](https://andrii.cloud/index.md) - [/colocation/](https://andrii.cloud/colocation/index.md) - [/about/](https://andrii.cloud/about/index.md) - [/faq/](https://andrii.cloud/faq/index.md) - [/interest/](https://andrii.cloud/interest/index.md) - [/terms/](https://andrii.cloud/terms/index.md) - [/colocation-terms/](https://andrii.cloud/colocation-terms/index.md) - [/acceptable-use/](https://andrii.cloud/acceptable-use/index.md) - [/privacy/](https://andrii.cloud/privacy/index.md) - [/sla/](https://andrii.cloud/sla/index.md) - [/abuse/](https://andrii.cloud/abuse/index.md) --- Andrii Co., a Washington for-profit corporation (UBI 604505773), doing business as Andrii Cloud · 11826 NE 167th St, Bothell WA 98011-5456 +1 877 987 7987 (call us — we don't text) · hello@andrii.cloud HTML version of this page: https://andrii.cloud/network/ · AI index: https://andrii.cloud/llms.txt · Full site text: https://andrii.cloud/llms-full.txt