157.228.152.0/24
At a glance
Addresses
/24 block
Visibility
73 of 76 vantage points
RPKI
Registry
AEAllocated 7th April 2004
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 AS204339seen on 4,056 paths from 134 vantage points
- Peer of AS214602seen on 428 paths from 121 vantage points
- Peer of AS9002seen on 164,437 paths from 32 vantage points
- Peer of AS6453seen on 653,228 paths from 6 vantage points
GB
US
FROne 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
- Amsterdam20433950113250918298This path
- London, UK2043395011369398529This path
- Sao Paulo2043392146029002645335280Shown above
- Singapore20433950113244823862323673This path
- Oregon, US2043392146029002855142013This 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
96%
Seen by 73 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- United Arab Emirates
- Allocated
- 7th April 2004
- Allocation block
- 157.228.128.0/18
- Status
- assigned
- 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.
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 |
|---|---|---|---|
| 157.228.153.0/24 | 256 | AS204339FIRST SERVER LIMITED | 73/76 |
History
- AS20433922nd 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 157.228.152.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.