5.182.120.0/24
At a glance
Addresses
/24 block
Visibility
55 of 76 vantage points
RPKI
Registry
USAllocated 8th April 2019
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 AS400810seen on 889 paths from 76 vantage points
- Peer of AS46475seen on 971 paths from 71 vantage points
- Peer of AS3491seen on 56,528 paths from 56 vantage points
- Peer of AS174seen on 156,544 paths from 1 vantage point
- Peer of AS8551seen on 1,076,486 paths from 1 vantage point
HK
IL
PSOne 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
- Amsterdam40081046475349182838298This path
- London, UK40081046475349112998529This path
- Sao Paulo400810464753491645335280This path
- Oregon, US400810464753491174855142013Shown 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
72%
Seen by 55 of 76 full-feed vantage points
Partially propagatedObserved at 4 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- United States
- Allocated
- 8th April 2019
- Allocation block
- 5.182.120.0/22
- 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 |
|---|---|---|---|
| 5.182.120.0/22 | 1k | AS397373H4Y Technologies LLC | 2/76 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 5.182.121.0/24 | 256 | AS397373H4Y Technologies LLC | 76/76 |
History
- AS4008109th November 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 5.182.120.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.