subnet.im

43.248.184.0/21

At a glance

Addresses

2,048

/21 block

Visibility

99%

77 of 78 vantage points

RPKI

Valid

Registry

Unknown

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

  1. London, UK56046980841348529This path
  2. Amsterdam635671337850131596928298This path
  3. Singapore6356713378501315969223673This path
  4. Sao Paulo63567133785013159692291435280This path
  5. 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 propagated

Observed 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

Route Origin Authorisations covering 43.248.184.0/21
ROA prefixAuthorised originMax length
43.248.184.0/21AS13378/21
43.248.184.0/21AS23650/21
43.248.184.0/21AS4134/21
43.248.184.0/21AS4837/21
43.248.184.0/21AS56046/21
43.248.184.0/21AS63567/21
43.248.184.0/21AS9808/21
43.248.176.0/20AS0/20

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

  1. AS6356712th October 2026 — present
  2. AS5604612th October 2026 — present
  3. AS48376th October 2026 — 12th October 2026
  4. AS635675th October 2026 — 6th October 2026
  5. AS483727th September 2026 — 6th October 2026
  6. AS635674th October 2026 — 5th October 2026
  7. AS6356725th September 2026 — 27th September 2026
  8. 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.