197.214.57.0/24
At a glance
Addresses
/24 block
Visibility
56 of 77 vantage points
RPKI
Registry
NEAllocated 29th November 2012
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS37531seen on 2,862 paths from 77 vantage points
- Peer of AS327708seen on 12,862 paths from 140 vantage points
- Peer of AS9498seen on 70,160 paths from 60 vantage points
- Peer of AS6453seen on 218,570 paths from 16 vantage points
- Peer of AS3491seen on 85,230 paths from 2 vantage points
RW
IN
US
HK
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.
Every path we see
- Amsterdam327708371008298This path
- London, UK3753132770894988529This path
- Oregon, US375313277089498693920130This path
- Sao Paulo3753132770894986453475535280This path
- Singapore3753132770894986453349123673Shown above
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
73%
Seen by 56 of 77 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
- Niger
- Allocated
- 29th November 2012
- Allocation block
- 197.214.0.0/18
- 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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 197.214.56.0/24 | 256 | AS36873Airtel Networks Limited | 77/77 |
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 197.214.57.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.