201.50.26.0/24
At a glance
Addresses
/24 block
Visibility
79 of 81 vantage points
RPKI
Registry
AEAllocated 6th March 2025
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 AS30042seen on 1,590 paths from 80 vantage points
- Peer of AS49592seen on 4,061 paths from 143 vantage points
- Peer of AS62255seen on 28,801 paths from 120 vantage points
- Peer of AS1299seen on 192,739 paths from 31 vantage points
- Peer of AS6939seen on 988,025 paths from 1 vantage point
US
GB
SI
SEOne 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, UK300424959262255129935280This path
- Sao Paulo300424959262255129935280This path
- Singapore300424959262255174132337This path
- Oregon, US3004249592622551299693920130Shown above
- Amsterdam30042495926225512993893082838298This 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
98%
Seen by 79 of 81 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
- 6th March 2025
- Allocation block
- 201.50.0.0/18
- 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 |
|---|---|---|
| 201.50.26.0/23 | AS834 | /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 |
|---|---|---|---|
| 201.50.27.0/24 | 256 | AS30042Boerboel LLC | 79/81 |
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 201.50.26.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.