158.51.155.0/24
At a glance
Addresses
/24 block
Visibility
24 of 80 vantage points
RPKI
Registry
USAllocated 10th January 2020
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS5065seen on 9,551 paths from 80 vantage points
- Peer of AS21859seen on 5,611 paths from 104 vantage points
- Peer of AS7195seen on 14,382 paths from 2 vantage points
- Peer of AS262355seen on 35,707 paths from 2 vantage points
CO
BROne 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
- London, UK5065218591374098529This path
- Singapore5065218596939132337This path
- Oregon, US506521859693920130This path
- Sao Paulo5065218597195262355266213Shown above
- Amsterdam50652185969395829941051213151This path
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
30%
Seen by 24 of 80 full-feed vantage points
Seen by few vantage pointsObserved 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
- 10th January 2020
- Allocation block
- 158.51.155.0/24
- Status
- allocated
- Origin validation
- Invalid
A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 158.51.155.0/24 | AS0 | /24 |
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 158.51.154.0/24 | 256 | AS14244NSI Hosting | 80/80 |
History
- AS506512th August 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 158.51.155.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.