199.204.25.0/24
At a glance
Addresses
/24 block
Visibility
81 of 81 vantage points
RPKI
Registry
GBAllocated 2nd April 2010
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS210814seen on 401 paths from 81 vantage points
- Peer of AS215120seen on 405 paths from 81 vantage points
- Peer of AS49581seen on 40,072 paths from 132 vantage points
- Peer of AS44592seen on 7,372 paths from 40 vantage points
- Peer of AS6453seen on 665,983 paths from 6 vantage points
AT
DE
NL
US
FROne 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
- Amsterdam21081421512049581445928298This path
- Singapore2108142151204958144592132337This path
- London, UK2108142151204958144592645335280Shown above
- Sao Paulo2108142151204958144592645335280This path
- Oregon, US2108142151204958144592693920130This 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 81 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- United Kingdom
- Allocated
- 2nd April 2010
- Allocation block
- 199.204.24.0/22
- 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 |
|---|---|---|
| 199.204.25.0/24 | AS210814 | /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 |
|---|---|---|---|
| 199.204.24.0/24 | 256 | AS16276OVH SAS | 81/81 |
History
- AS21081422nd September 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 199.204.25.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.