SUBNET.IM

67.101.48.0/20

Telecom Italia Sparkle (Seabone)AS6762

At a glance

Addresses

4,096

/20 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

ARINUS

Allocated 18th April 2003

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 67.101.48.0/20 as seen from Singapore, read outward from the origin: AS6762 → AS6939 → AS132337. Each hop is listed with its network name beneath the graph.AS6762Telecom Italia Sp…OriginAS6939Hurricane Electri…AS132337Axclusive

Seen from Singapore

  1. 1AS6762Telecom Italia Sparkle (Seabone)ITOrigin
    Peer of AS6762seen on 144,819 paths from 33 vantage points
  2. 2AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 320,794 paths from 2 vantage points
  3. 3AS132337AxclusiveSGVantage 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. London, UK67628529This path
  2. Sao Paulo67623356266213This path
  3. Singapore67626939132337Shown above
  4. Oregon, US6762693920130This path
  5. Amsterdam676217434549213151This 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

100%

Seen by 80 of 80 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
ARIN — North America
Country
United States
Allocated
18th April 2003
Allocation block
67.100.0.0/14
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 67.101.48.0/20: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.67.101.32.0/19AS607967.101.0.0/18AS702967.101.0.0/18AS2011567.101.0.0/17AS2011567.100.0.0/14AS325767.101.48.0/20AS6762This prefix67.101.32.0/20AS6762

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.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 67.101.48.0/20
PrefixAddressesOriginVisibility
67.101.32.0/204.1kAS6762Telecom Italia Sparkle (Seabone)80/80

History

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

Open 67.101.48.0/20 in the calculator/20 reference

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