175.111.2.0/24
At a glance
Addresses
/24 block
Visibility
79 of 80 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 AS198247seen on 1,959 paths from 142 vantage points
- Peer of AS208428seen on 2,924 paths from 80 vantage points
- Peer of AS198949seen on 260 paths from 18 vantage points
- Peer of AS6939seen on 320,794 paths from 2 vantage points
AE
IL
US
SGOne 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, UK1982472084281989498529This path
- Singapore1982472084281989496939132337Shown above
- Oregon, US198247208428198949693920130This path
- Amsterdam198247208428198949129934549213151This path
- Sao Paulo19824720842819894912993356266213This 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
99%
Seen by 79 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
- 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 | AS198247 | /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 | 80/80 |
History
- AS19824712th 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 175.111.2.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.