156.247.124.0/24
At a glance
Addresses
/24 block
Visibility
81 of 81 vantage points
RPKI
Registry
SCAllocated 22nd December 2015
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS9294seen on 33,003 paths from 81 vantage points
- Peer of AS18013seen on 35,513 paths from 81 vantage points
- Peer of AS17476seen on 27,667 paths from 145 vantage points
- Peer of AS2914seen on 448,517 paths from 6 vantage points
US
HK
FROne 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
- Singapore92941801317476132337This path
- London, UK92941801317476129935280This path
- Sao Paulo92941801317476291435280Shown above
- Amsterdam929418013174761299250918298This path
- Oregon, US929418013174761299693920130This 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
100%
Seen by 81 of 81 full-feed vantage points
Globally 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
- Seychelles
- Allocated
- 22nd December 2015
- Allocation block
- 156.224.0.0/11
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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 |
|---|---|---|---|
| 156.247.112.0/20 | 4.1k | AS9294GNET INC. | 81/81 |
| 156.247.64.0/18 | 16.4k | AS9294GNET INC. | 81/81 |
| 156.247.0.0/16 | 65.5k | AS35916MULTACOM CORPORATION | 81/81 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 156.247.125.0/24 | 256 | AS9294GNET INC. | 80/81 |
History
- AS929422nd September 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 156.247.124.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.