SUBNET.IM

2607:1640:1031:1::200/127

PEER 1031 LLCAS1031

At a glance

Subnets

Unknown

/127 block

Visibility

2%

1 of 62 vantage points

RPKI

No ROA

Registry

ARINUS

Allocated 20th December 2022

AS paths to this prefix

No AS paths are stored for this prefix. We keep the full path from one reference peer per collector rather than from every peer, so a prefix only has paths here once it has been seen by one of those peers.

Route visibility

2%

Seen by 1 of 62 full-feed vantage points

Seen by few vantage points

Observed at 1 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
United States
Allocated
20th December 2022
Allocation block
2607:1640::/32
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2607:1640:1031:1::200/127: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2607:1640::/32AS9992607:1640::/32AS10312607:1640:1031:1…AS1031This prefix2607:1640:1031:1…AS1031

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 2607:1640:1031:1::200/127
PrefixAddressesOriginVisibility
2607:1640::/324.3B × /64AS999CORIX NETWORKS58/62
2607:1640::/324.3B × /64AS1031PEER 1031 LLC2/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2607:1640:1031:1::200/127
PrefixAddressesOriginVisibility
2607:1640:1031:1::202/1272AS1031PEER 1031 LLC1/62

History

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