43.248.184.0/21
Suqian Pugongying Network Service Co.,LtdAS63567
China Mobile Jiangsu Province NetworkAS56046
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/21 block
Visibility
77 of 78 vantage points
RPKI
Registry
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 AS63567seen on 389 paths from 78 vantage points
- Peer of AS13378seen on 149 paths from 37 vantage points
- Peer of AS50131seen on 284 paths from 77 vantage points
- Peer of AS59692seen on 8,651 paths from 46 vantage points
- Peer of AS2914seen on 440,998 paths from 6 vantage points
CN
US
GB
AE
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
- London, UK56046980841348529This path
- Amsterdam635671337850131596928298This path
- Singapore6356713378501315969223673This path
- Sao Paulo63567133785013159692291435280Shown above
- Oregon, US6356713378559333223855142013This 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
99%
Seen by 77 of 78 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
- Unknown
- Country
- Unknown
- Allocated
- Unknown
- Allocation block
- Unknown
- Status
- Unknown
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
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
- AS6356712th October 2026 — present
- AS5604612th October 2026 — present
- AS48376th October 2026 — 12th October 2026
- AS635675th October 2026 — 6th October 2026
- AS483727th September 2026 — 6th October 2026
- AS635674th October 2026 — 5th October 2026
- AS6356725th September 2026 — 27th September 2026
- AS483723rd September 2026 — 24th September 2026
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.248.184.0/21 in the calculator/21 reference
Routing data derived from RouteViews MRT archives and public registry data.