88.223.212.0/24
At a glance
Addresses
/24 block
Visibility
5 of 76 vantage points
RPKI
Registry
LTAllocated 7th February 2006
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Adjacentseen on 2 paths from 1 vantage point
- Peer of AS45899seen on 1,857 paths from 2 vantage points
- Peer of AS55329seen on 11,345 paths from 2 vantage points
NL
VN
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.
Route visibility
7%
Seen by 5 of 76 full-feed vantage points
Seen by few vantage pointsObserved at 2 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
- Lithuania
- Allocated
- 7th February 2006
- Allocation block
- 88.222.0.0/15
- 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.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 88.223.212.0/23 | AS49453 | /23 |
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 |
|---|---|---|---|
| 88.223.212.0/23 | 512 | AS49453Global Layer B.V. | 76/76 |
| 88.223.208.0/20 | 4.1k | AS62387meerfarbig GmbH & Co. KG | 76/76 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 88.223.213.0/24 | 256 | AS49453Global Layer B.V. | 5/76 |
History
- AS494536th November 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 88.223.212.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.