SUBNET.IM

2605:de40:300::/40

FGLTEL Inc.AS46091

At a glance

Subnets

16,777,216 × /64

/40 block

Visibility

97%

60 of 62 vantage points

RPKI

Valid

Registry

ARINCA

Allocated 27th July 2020

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.

OriginVantage points
AS path graph: 4 observed paths to 2605:de40:300::/40, fanning out from AS46091 toward the vantage points that see it. Each path is written out in full beneath the graph.AS46091FGLTEL Inc.OriginAS6461Zayo BandwidthAS34549meerfarbig GmbH &…AS213151Christian ElsenAS174Cogent Communicat…AS15576NTS workspace AGAS51907Kanton ZugAS12956Telxius (Telefoni…AS32590Valve CorporationAS6939Hurricane Electri…AS132337Axclusive
  1. Amsterdam46091646134549213151This path
  2. London, UK460911741557651907This path
  3. Sao Paulo460911741295632590This path
  4. Singapore4609164616939132337This 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

97%

Seen by 60 of 62 full-feed vantage points

Globally 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
ARIN — North America
Country
Canada
Allocated
27th July 2020
Allocation block
2605:de40::/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 2605:de40:300::/40
ROA prefixAuthorised originMax length
2605:de40::/32AS397553/32
2605:de40::/32AS46091/64

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 2605:de40:300::/40: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2605:de40::/32AS460912605:de40:300::/…AS46091This prefix2605:de40:200::/…AS46091

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

Announcements that contain 2605:de40:300::/40
PrefixAddressesOriginVisibility
2605:de40::/324.3B × /64AS46091FGLTEL Inc.60/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2605:de40:300::/40
PrefixAddressesOriginVisibility
2605:de40:200::/4016.8M × /64AS46091FGLTEL Inc.60/62

History

  1. AS4609112th 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.