213.218.216.0/24
AS18186 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Addresses
/24 block
Visibility
1 of 76 vantage points
RPKI
Registry
GBAllocated 13th January 2003
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Oregon, US.
Seen from Oregon, US
- Peer of AS136725seen on 9 paths from 1 vantage point
- Peer of AS63199seen on 5,954 paths from 118 vantage points
- Peer of AS3257seen on 66,143 paths from 17 vantage points
- Peer of AS6762seen on 32,980 paths from 1 vantage point
- Peer of AS1680seen on 35,288 paths from 1 vantage point
CN
US
IT
IL
PSOne 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.
Route visibility
1%
Seen by 1 of 76 full-feed vantage points
Seen by few vantage pointsObserved at 1 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
- 13th January 2003
- Allocation block
- 213.218.208.0/20
- Status
- allocated
- Origin validation
- Invalid
A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.
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 |
|---|---|---|---|
| 213.218.208.0/20 | 4.1k | AS8851GCI Network Solutions Limited | 1/76 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 213.218.217.0/24 | 256 | AS8851GCI Network Solutions Limited | 76/76 |
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 213.218.216.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.