45.62.168.0/24
Alejandro Uballe MontoyaAS270168
Announced by more than one origin AS (MOAS).
AS401776 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Addresses
/24 block
Visibility
80 of 81 vantage points
RPKI
Registry
USAllocated 7th July 2022
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS270168seen on 587 paths from 144 vantage points
- Peer of AS270158seen on 4,898 paths from 111 vantage points
- Peer of AS174seen on 705,121 paths from 82 vantage points
- Peer of AS1299seen on 341,460 paths from 5 vantage points
- Peer of AS25091seen on 666,530 paths from 2 vantage points
MX
SE
CHOne 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
- Singapore2701682701586939132337This path
- Oregon, US270168270158693920130This path
- London, UK270168270158174129935280This path
- Sao Paulo270168270158174645335280This path
- Amsterdam2701682701581741299250918298Shown 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
99%
Seen by 80 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
- ARIN — North America
- Country
- United States
- Allocated
- 7th July 2022
- Allocation block
- 45.62.160.0/20
- 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.62.168.0/24 | AS270168 | /24 |
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 |
|---|---|---|---|
| 45.62.168.0/23 | 512 | AS51847Nearoute Limited | 81/81 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 45.62.169.0/24 | 256 | AS9304HGC Global Communications Limited | 81/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 45.62.168.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.