188.220.41.0/24
Not announced at this prefix length
No announcement covering 188.220.41.0/24 was visible from any of our collectors at the last snapshot. That can mean the space is unrouted, or that it is announced only within a network we have no vantage point inside.
At a glance
Addresses
/24 block
Visibility
RPKI
Registry
GBAllocated 26th May 2009
AS paths to this prefix
No AS paths are stored for this prefix. We keep the full path from one reference peer per collector rather than from every peer, so a prefix only has paths here once it has been seen by one of those peers.
Registry and RPKI
- RIR
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- United Kingdom
- Allocated
- 26th May 2009
- Allocation block
- 188.220.0.0/14
- Status
- allocated
- Origin validation
- Unknown
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 188.220.41.0/24 | AS834 | /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 |
|---|---|---|---|
| 188.220.40.0/24 | 256 | AS6762Telecom Italia Sparkle (Seabone) | 80/81 |
History
- AS21387622nd September 2026 — 24th 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 188.220.41.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.