43.109.27.0/24
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
SGAllocated 21st February 1989
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 AS24429seen on 215 paths from 139 vantage points
- Peer of AS58715seen on 12,815 paths from 139 vantage points
- Peer of AS9498seen on 70,135 paths from 62 vantage points
- Peer of AS6453seen on 15,692 paths from 6 vantage points
- Peer of AS4755seen on 93,650 paths from 6 vantage points
CN
BD
IN
US
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
- Amsterdam244295871594988298This path
- London, UK244295871594988529This path
- Singapore2442958715949823673This path
- Oregon, US24429587159498855142013This path
- Sao Paulo244295871594986453475535280Shown 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
100%
Seen by 76 of 76 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
- APNIC — Asia-Pacific
- Country
- Singapore
- Allocated
- 21st February 1989
- Allocation block
- 43.0.0.0/9
- 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.
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 |
|---|---|---|---|
| 43.109.26.0/24 | 256 | AS24429Alibaba Cloud | 76/76 |
History
- AS244294th October 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 43.109.27.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.