195.72.188.0/24
At a glance
Addresses
/24 block
Visibility
77 of 77 vantage points
RPKI
Registry
GBAllocated 30th September 1997
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS213840seen on 1,132 paths from 77 vantage points
- Peer of AS1002seen on 2,765 paths from 77 vantage points
- Peer of AS137409seen on 9,222 paths from 2 vantage points
US
AU
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
- Amsterdam21384010021374098298This path
- London, UK21384010021374098529This path
- Sao Paulo213840100213740935280This path
- Singapore213840100213740923673Shown above
- Oregon, US2138401002137409693920130This 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 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- United Kingdom
- Allocated
- 30th September 1997
- Allocation block
- 195.72.160.0/19
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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 |
|---|---|---|---|
| 195.72.160.0/19 | 8.2k | AS3257GTT Communications Inc. | 77/77 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 195.72.189.0/24 | 256 | AS213840DDOS PROTECTION LTD | 77/77 |
History
- AS21384020th October 2026 — present
- AS879619th October 2026 — 19th October 2026
- AS21384025th September 2026 — 19th October 2026
- AS879625th September 2026 — 6th October 2026
- AS748830th September 2026 — 4th October 2026
- AS748823rd September 2026 — 25th September 2026
- AS879622nd September 2026 — 25th September 2026
- AS748822nd September 2026 — 22nd September 2026
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 195.72.188.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.