175.111.2.0/24
At a glance
Addresses
/24 block
Visibility
77 of 77 vantage points
RPKI
Registry
PKAllocated 12th January 2010
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS24435seen on 1,808 paths from 139 vantage points
- Peer of AS138423seen on 17,993 paths from 139 vantage points
- Peer of AS17557seen on 31,592 paths from 47 vantage points
- Peer of AS6939seen on 358,340 paths from 2 vantage points
US
KHOne 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
- Amsterdam24435381938298This path
- London, UK24435381938529This path
- Sao Paulo2443538193423035280This path
- Oregon, US2443538193855142013This path
- Singapore2443513842317557693923673Shown 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
100%
Seen by 77 of 77 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
- APNIC — Asia-Pacific
- Country
- Pakistan
- Allocated
- 12th January 2010
- Allocation block
- 175.111.0.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 |
|---|---|---|
| 175.111.2.0/24 | AS24435 | /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 |
|---|---|---|---|
| 175.111.3.0/24 | 256 | AS24435Supernet Limited Transit Autonomous System Number | 77/77 |
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 175.111.2.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.