subnet.im

2a10:fa82:fef0::/44

At a glance

Subnets

1,048,576 × /64

/44 block

Visibility

29%

18 of 63 vantage points

RPKI

Valid

Registry

RIPE NCCRO

Allocated 25th January 2021

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 2a10:fa82:fef0::/44 as seen from Singapore, read outward from the origin: AS205941 → AS6204 → AS174 → AS132337. Each hop is listed with its network name beneath the graph.AS205941Lungu Stefan Gabr…OriginAS6204INTERKVM HOST SRLAS174Cogent Communicat…AS132337Axclusive

Seen from Singapore

  1. Peer of AS205941seen on 577 paths from 86 vantage points
  2. Peer of AS6204seen on 5,977 paths from 91 vantage points
  3. Peer of AS174seen on 84,081 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage 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. Singapore2059416204174132337Shown 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

29%

Seen by 18 of 63 full-feed vantage points

Seen by few vantage points

Observed at 2 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
Romania
Allocated
25th January 2021
Allocation block
2a10:fa80::/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:fa82:fef0::/44
ROA prefixAuthorised originMax length
2a10:fa82:fef0::/44AS205941/44
2a10:fa82:fe00::/40AS205941/40
2a10:fa82::/32AS205941/32

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2a10:fa82:fef0::/44: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2a10:fa82:fe00::…AS2059412a10:fa82::/32AS2059412a10:fa82:fef0::…AS205941This prefix

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 2a10:fa82:fef0::/44
PrefixAddressesOriginVisibility
2a10:fa82:fe00::/4016.8M × /64AS205941Lungu Stefan Gabriel62/63
2a10:fa82::/324.3B × /64AS205941Lungu Stefan Gabriel62/63

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS2059417th November 2026 — present
  2. AS20594120th October 2026 — 6th November 2026
  3. AS20594118th October 2026 — 20th October 2026
  4. AS20594115th October 2026 — 18th October 2026
  5. AS20594112th October 2026 — 15th October 2026
  6. AS20594112th August 2026 — 7th October 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.