184.174.51.0/24
AS402306 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Addresses
/24 block
Visibility
75 of 76 vantage points
RPKI
Registry
USAllocated 25th October 2010
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 AS136809seen on 3,602 paths from 75 vantage points
- Peer of AS62610seen on 41,308 paths from 138 vantage points
- Peer of AS29752seen on 14,737 paths from 137 vantage points
- Peer of AS3257seen on 59,610 paths from 1 vantage point
- Peer of AS23352seen on 105,644 paths from 1 vantage point
BDOne 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
- Amsterdam136809626102975242298298This path
- London, UK136809626102975242298529This path
- Sao Paulo13680962610297523257645335280This path
- Singapore136809626102975242295746323673This path
- Oregon, US136809626102975232572335220130Shown 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
99%
Seen by 75 of 76 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
- 25th October 2010
- Allocation block
- 184.174.0.0/17
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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 |
|---|---|---|---|
| 184.174.0.0/17 | 32.8k | AS21769Colocation America Corporation | 75/76 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 184.174.50.0/24 | 256 | AS211373Simoresta UAB | 76/76 |
History
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 184.174.51.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.