subnet.im

2405:4cc1:300::/40

CHRISTIAN CONGREGATION OF JEHOVAH'S WITNESSES (AUSTRALASIA) LIMITEDAS149778

At a glance

Subnets

16,777,216 × /64

/40 block

Visibility

42%

26 of 62 vantage points

RPKI

Valid

Registry

APNICAU

Allocated 1st October 2019

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Amsterdam.

OriginVantage point · Amsterdam
One AS path to 2405:4cc1:300::/40 as seen from Amsterdam, read outward from the origin: AS149778 → AS9326 → AS147168 → AS6939 → AS213151. Each hop is listed with its network name beneath the graph.AS149778CHRISTIAN CONGREG…OriginAS9326PT Centrin UtamaAS147168PT NTT IndonesiaAS6939Hurricane Electri…AS213151Christian Elsen

Seen from Amsterdam

  1. 1AS149778CHRISTIAN CONGREGATION OF JEHOVAH'S WITNESSES (AUSTRALASIA) LIMITEDAUOrigin
    Peer of AS149778seen on 26 paths from 26 vantage points
  2. 2AS9326PT Centrin UtamaID
    Peer of AS9326seen on 398 paths from 31 vantage points
  3. 3AS147168PT NTT IndonesiaID
    Peer of AS147168seen on 64 paths from 21 vantage points
  4. 4AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 309,709 paths from 2 vantage points
  5. 5AS213151Christian ElsenDEVantage point

One 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

  1. Singapore1497789326147168132337This path
  2. Amsterdam14977893261471686939213151Shown above
  3. Sao Paulo1497789326147168693932590This path
  4. London, UK149778932613884082201557651907This 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

42%

Seen by 26 of 62 full-feed vantage points

Partially propagated

Observed at 4 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
Australia
Allocated
1st October 2019
Allocation block
2405:4cc1::/32
Status
allocated
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 2405:4cc1:300::/40
ROA prefixAuthorised originMax length
2405:4cc1:300::/40AS149778/40
2405:4cc1:300::/40AS55891/40

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

Prefixes of the same length sharing a parent block with 2405:4cc1:300::/40
PrefixAddressesOriginVisibility
2405:4cc1:200::/4016.8M × /64AS55891WATCH TOWER BIBLE AND TRACT SOCIETY62/62

History

  1. AS14977812th August 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.

Routing data derived from RouteViews MRT archives and public registry data.