45.134.99.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
IRAllocated 13th February 2025
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS201150seen on 1,759 paths from 80 vantage points
- Peer of AS49100seen on 31,517 paths from 80 vantage points
- Peer of AS43754seen on 152,403 paths from 142 vantage points
- Peer of AS41689seen on 152,403 paths from 142 vantage points
- Peer of AS49666seen on 74,980 paths from 142 vantage points
- Peer of AS6762seen on 52,053 paths from 31 vantage points
- Peer of AS174seen on 181,897 paths from 3 vantage points
- Peer of AS34549seen on 716,762 paths from 2 vantage points
IT
US
DEOne 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
- Singapore201150491004375441689496666939132337This path
- Oregon, US20115049100437544168949666693920130This path
- Amsterdam20115049100437544168949666676217434549→ ⋯Shown above
- London, UK20115049100437544168949666676212998529This path
- Sao Paulo2011504910043754416894966667623356266213This 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
100%
Seen by 80 of 80 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
- Iran
- Allocated
- 13th February 2025
- Allocation block
- 45.134.99.0/24
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 45.134.99.0/24 | AS201150 | /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 |
|---|---|---|---|
| 45.134.98.0/24 | 256 | AS138643XINYUAN INTERCONNECT COMPANY LTD | 80/80 |
History
- AS20115012th 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 45.134.99.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.