subnet.im

2806:1060:b08::/48

Instituto Mexicano de la Propiedad IndustrialAS270181

At a glance

Subnets

65,536 × /64

/48 block

Visibility

14%

9 of 63 vantage points

RPKI

Invalid

Registry

LACNICMX

Allocated 1st March 2011

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

14%

Seen by 9 of 63 full-feed vantage points

Seen by few vantage points

Observed at 3 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
LACNIC — Latin America and the Caribbean
Country
Mexico
Allocated
1st March 2011
Allocation block
2806:1000::/24
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 2806:1060:b08::/48
ROA prefixAuthorised originMax length
2806:1000::/24AS8151/48

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2806:1060:b08::/48: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2806:1060::/32AS81512806:1060:b08::/…AS270181This prefix2806:1060:b09::/…AS8151

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 2806:1060:b08::/48
PrefixAddressesOriginVisibility
2806:1060::/324.3B × /64AS8151Telmex (Uninet)62/63

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2806:1060:b08::/48
PrefixAddressesOriginVisibility
2806:1060:b09::/4865.5k × /64AS8151Telmex (Uninet)62/63

History

  1. AS2701817th November 2026 — present
  2. AS2701816th November 2026 — 6th November 2026
  3. AS2701815th November 2026 — 5th November 2026
  4. AS27018126th October 2026 — 4th November 2026
  5. AS27018116th October 2026 — 25th October 2026
  6. AS27018126th September 2026 — 16th October 2026
  7. AS27018124th September 2026 — 25th September 2026
  8. AS27018112th August 2026 — 23rd September 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.