subnet.im

2a12:bec4:1d30::/44

Vladyslav KobaAS197324

At a glance

Subnets

1,048,576 × /64

/44 block

Visibility

2%

1 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCGB

Allocated 1st April 2022

AS paths to this prefix

All paths

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

OriginVantage point · Sao Paulo
One AS path to 2a12:bec4:1d30::/44 as seen from Sao Paulo, read outward from the origin: AS197324 → AS214757 → AS49127 → AS137409 → AS6461 → AS6939 → AS32590. Each hop is listed with its network name beneath the graph.AS197324Vladyslav KobaOriginAS214757Jakub KrsaAS49127Asimo Networks B.…AS137409GSL Networks Pty …AS6461Zayo BandwidthAS6939Hurricane Electri…AS32590Valve Corporation

Seen from Sao Paulo

  1. 1AS197324Vladyslav KobaILOrigin
    Peer of AS197324seen on 3 paths from 1 vantage point
  2. 2AS214757Jakub KrsaCZ
    Peer of AS214757seen on 485 paths from 61 vantage points
  3. 3AS49127Asimo Networks B.V.NL
    Peer of AS49127seen on 5,749 paths from 117 vantage points
  4. 4AS137409GSL Networks Pty LTDAU
    Peer of AS137409seen on 25,913 paths from 110 vantage points
  5. 5AS6461Zayo BandwidthUS
    Peer of AS6461seen on 51,122 paths from 26 vantage points
  6. 6AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 335,352 paths from 8 vantage points
  7. 7AS32590Valve CorporationUSVantage 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. Sao Paulo197324214757491271374096461693932590Shown above

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.

Route visibility

2%

Seen by 1 of 62 full-feed vantage points

Seen by few vantage points

Observed at 1 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
United Kingdom
Allocated
1st April 2022
Allocation block
2a12:bec0::/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 2a12:bec4:1d30::/44
ROA prefixAuthorised originMax length
2a12:bec4:1d30::/44AS197324/44

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 2a12:bec4:1d30::/44
PrefixAddressesOriginVisibility
2a12:bec4:1d20::/441M × /64AS197324Vladyslav Koba1/62

History

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