subnet.im

2608:1c1::/48

Microsoft (Azure Customer Peering)AS12076

At a glance

Subnets

65,536 × /64

/48 block

Visibility

97%

61 of 63 vantage points

RPKI

No ROA

Registry

ARINUS

Allocated 6th May 2008

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 2608:1c1::/48 as seen from London, UK, read outward from the origin: AS12076 → AS5852 → AS27064 → AS721 → AS3356 → AS35280. Each hop is listed with its network name beneath the graph.AS12076Microsoft (Azure …OriginAS5852United States Dep…AS27064Defense Informati…AS721United States Dep…AS3356Lumen (Level 3)AS35280F5 Networks SARL

Seen from London, UK

  1. 1AS12076Microsoft (Azure Customer Peering)USOrigin
    Peer of AS12076seen on 370 paths from 62 vantage points
  2. 2AS5852United States Department of Defense (DoD)US
    Peer of AS5852seen on 68,807 paths from 138 vantage points
  3. 3AS27064Defense Information Systems Agency (DISA)US
    Peer of AS27064seen on 770,165 paths from 138 vantage points
  4. 4AS721United States Department of Defense (DoD)US
    Peer of AS721seen on 987,286 paths from 138 vantage points
  5. 5AS3356Lumen (Level 3)US
    Peer of AS3356seen on 838,868 paths from 6 vantage points
  6. 6AS35280F5 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, UK12076585227064721335635280Shown above
  2. Amsterdam120765852270647213356250918298This path
  3. Sao Paulo120765852270647213356645335280This path
  4. Singapore1207658522706472133566939132337This 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 61 of 63 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
United States
Allocated
6th May 2008
Allocation block
2608::/22
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 2608:1c1::/48
PrefixAddressesOriginVisibility
2608:1c1:1::/4865.5k × /64AS12076Microsoft (Azure Customer Peering)62/63

History

  1. AS120766th November 2026 — present
  2. AS1207622nd September 2026 — 5th November 2026
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.