subnet.im

2a10:3c0:2::/48

NSEC - Sistemas Informaticos, S.A.AS211680

At a glance

Subnets

65,536 × /64

/48 block

Visibility

95%

61 of 64 vantage points

RPKI

Valid

Registry

RIPE NCCPT

Allocated 4th March 2020

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 2a10:3c0:2::/48 as seen from London, UK, read outward from the origin: AS211680 → AS32475 → AS6461 → AS35280. Each hop is listed with its network name beneath the graph.AS211680NSEC - Sistemas I…OriginAS32475Internap Holding …AS6461Zayo BandwidthAS35280F5 Networks SARL

Seen from London, UK

  1. 1AS211680NSEC - Sistemas Informaticos, S.A.PTOrigin
    Peer of AS211680seen on 496 paths from 141 vantage points
  2. 2AS32475Internap Holding LLCUS
    Peer of AS32475seen on 6,185 paths from 141 vantage points
  3. 3AS6461Zayo BandwidthUS
    Peer of AS6461seen on 38,472 paths from 6 vantage points
  4. 4AS35280F5 Networks SARLFRVantage 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, UK21168032475646135280Shown above
  2. Amsterdam211680324756461250918298This path
  3. Sao Paulo21168032475174645335280This path
  4. Singapore2116803247564616939132337This 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

95%

Seen by 61 of 64 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
Portugal
Allocated
4th March 2020
Allocation block
2a10:3c0::/29
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 2a10:3c0:2::/48
ROA prefixAuthorised originMax length
2a10:3c0:2::/48AS211680/48

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 2a10:3c0:2::/48
PrefixAddressesOriginVisibility
2a10:3c0:3::/4865.5k × /64AS21859Zenlayer Inc62/64

History

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