subnet.im

2a07:bcc0::/48

AB NET S.R.L.AS35146

At a glance

Subnets

65,536 × /64

/48 block

Visibility

100%

62 of 62 vantage points

RPKI

No ROA

Registry

RIPE NCCIT

Allocated 21st July 2016

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 2a07:bcc0::/48 as seen from Singapore, read outward from the origin: AS35146 → AS39479 → AS50316 → AS132337. Each hop is listed with its network name beneath the graph.AS35146AB NET S.R.L.OriginAS39479NS3 s.r.l.AS50316Net Global SrlAS132337Axclusive

Seen from Singapore

  1. 1AS35146AB NET S.R.L.ITOrigin
    Peer of AS35146seen on 222 paths from 142 vantage points
  2. 2AS39479NS3 s.r.l.IT
    Peer of AS39479seen on 541 paths from 87 vantage points
  3. 3AS50316Net Global SrlIT
    Peer of AS50316seen on 135 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage 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. Amsterdam351463947950316213151This path
  2. London, UK35146394795031651907This path
  3. Singapore351463947950316132337Shown above
  4. Sao Paulo351463947950316719532590This 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 62 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Italy
Allocated
21st July 2016
Allocation block
2a07:bcc0::/29
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.

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 2a07:bcc0::/48
PrefixAddressesOriginVisibility
2a07:bcc0:1::/4865.5k × /64AS35146AB NET S.R.L.62/62

History

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