subnet.im

2a0d:3dc1:4a67::/48

Antonios A. CharitonAS210312

At a glance

Subnets

65,536 × /64

/48 block

Visibility

13%

8 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCGR

Allocated 28th August 2018

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 2a0d:3dc1:4a67::/48 as seen from Singapore, read outward from the origin: AS210312 → AS4601 → AS8298 → AS25091 → AS6453 → AS9002 → AS132337. Each hop is listed with its network name beneath the graph.AS210312Antonios A. Chari…OriginAS4601Antonios A. Chari…AS8298IPng Networks GmbHAS25091IP-Max SAAS6453TATA Communicatio…AS9002RETN LimitedAS132337Axclusive

Seen from Singapore

  1. 1AS210312Antonios A. CharitonGROrigin
    Peer of AS210312seen on 1,287 paths from 61 vantage points
  2. 2AS4601Antonios A. CharitonGR
    Peer of AS4601seen on 1,668 paths from 113 vantage points
  3. 3AS8298IPng Networks GmbHCH
    Peer of AS8298seen on 2,055 paths from 98 vantage points
  4. 4AS25091IP-Max SACH
    Peer of AS25091seen on 3,195 paths from 45 vantage points
  5. 5AS6453TATA Communications (America) IncUS
    Peer of AS6453seen on 241,792 paths from 25 vantage points
  6. 6AS9002RETN LimitedGB
    Peer of AS9002seen on 45,093 paths from 2 vantage points
  7. 7AS132337AxclusiveSGVantage 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. Singapore210312460182982509164539002132337Shown 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

13%

Seen by 8 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
Greece
Allocated
28th August 2018
Allocation block
2a0d:3dc0::/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 2a0d:3dc1:4a67::/48
ROA prefixAuthorised originMax length
2a0d:3dc1::/32AS210312/48
2a0d:3dc1::/32AS4601/48
2a0d:3dc0::/30AS0/128
2a0d:3dc0::/29AS4601/29

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2a0d:3dc1:4a67::/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.2a0d:3dc0::/29AS46012a0d:3dc1:4a67::…AS210312This prefix2a0d:3dc1:4a66::…AS210312

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 2a0d:3dc1:4a67::/48
PrefixAddressesOriginVisibility
2a0d:3dc0::/2934.4B × /64AS4601Antonios A. Chariton61/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2a0d:3dc1:4a67::/48
PrefixAddressesOriginVisibility
2a0d:3dc1:4a66::/4865.5k × /64AS210312Antonios A. Chariton8/62

History

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