55.2.213.0/24
At a glance
Addresses
/24 block
Visibility
77 of 77 vantage points
RPKI
Registry
USAllocated 26th October 1996
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Oregon, US.
Seen from Oregon, US
- Peer of AS344seen on 13,613 paths from 140 vantage points
- Peer of AS306seen on 129,716 paths from 140 vantage points
- Peer of AS1540seen on 21,953 paths from 140 vantage points
- Peer of AS367seen on 41,987 paths from 140 vantage points
- Peer of AS27064seen on 790,169 paths from 140 vantage points
- Peer of AS721seen on 1,011,584 paths from 140 vantage points
- Peer of AS3356seen on 281,650 paths from 59 vantage points
- Peer of AS6939seen on 994,894 paths from 1 vantage point
One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.
Every path we see
- Amsterdam344306154036727064721335625091→ ⋯This path
- London, UK34430615403672706472133568529This path
- Sao Paulo344306154036727064721335635280This path
- Singapore344306154036727064721335623673This path
- Oregon, US34430615403672706472133566939→ ⋯Shown above
Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.
Route visibility
100%
Seen by 77 of 77 full-feed vantage points
Globally propagatedObserved at 5 of our collectors.
What this percentage counts
The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.
It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.
Registry and RPKI
- RIR
- ARIN — North America
- Country
- United States
- Allocated
- 26th October 1996
- Allocation block
- 55.0.0.0/8
- Status
- allocated
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 55.2.0.0/16 | 65.5k | AS344United States Department of Defense (DoD) | 77/77 |
| 55.0.0.0/8 | 16.8M | AS721United States Department of Defense (DoD) | 76/77 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 55.2.212.0/24 | 256 | AS344United States Department of Defense (DoD) | 77/77 |
History
- AS34422nd September 2026 — present
Why these dates start where they do
A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.
Open 55.2.213.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.