102.212.212.0/24
STE LEYA TECH + SOLUTION SARL (L.T.S SARL)AS329269
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
64 of 80 vantage points
RPKI
Registry
CDAllocated 6th June 2023
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS37447seen on 647 paths from 80 vantage points
- Peer of AS37273seen on 2,464 paths from 62 vantage points
- Peer of AS58453seen on 991 paths from 2 vantage points
UG
HK
SGOne 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
- London, UK32926937447308448529This path
- Singapore374473727358453132337Shown above
- Amsterdam3292693744730844325734549213151This path
- Sao Paulo329269374473084432573356266213This path
- Oregon, US32926937447308445511693920130This 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
80%
Seen by 64 of 80 full-feed vantage points
Partially 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
- AFRINIC — Africa
- Country
- Congo - Kinshasa
- Allocated
- 6th June 2023
- Allocation block
- 102.212.212.0/22
- Status
- allocated
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
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
No prefix of the same length in the same parent block is announced.
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 102.212.212.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.