subnet.im

2a13:9500:1bf::/48

INFRA SERVICOS TERCEIRIZADOS & TECNOLOGIA LTDAAS211087

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

63 of 64 vantage points

RPKI

Valid

Registry

RIPE NCCGB

Allocated 7th February 2023

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 2a13:9500:1bf::/48 as seen from Singapore, read outward from the origin: AS211087 → AS271200 → AS199829 → AS22356 → AS132337. Each hop is listed with its network name beneath the graph.AS211087INFRA SERVICOS TE…OriginAS271200TECNET BRASIL TEL…AS199829Akronic Network L…AS22356Durand do Brasil …AS132337Axclusive

Seen from Singapore

  1. 1AS211087INFRA SERVICOS TERCEIRIZADOS & TECNOLOGIA LTDABROrigin
    Peer of AS211087seen on 127 paths from 64 vantage points
  2. 2AS271200TECNET BRASIL TELECOMUNICACOES LTDABR
    Peer of AS271200seen on 622 paths from 144 vantage points
  3. 3AS199829Akronic Network LTDABR
    Peer of AS199829seen on 3,225 paths from 135 vantage points
  4. 4AS22356Durand do Brasil LtdaBR
    Peer of AS22356seen on 861 paths from 2 vantage points
  5. 5AS132337AxclusiveSGVantage 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 Paulo21108727120019982935280This path
  2. London, UK2110872712001998292235635280This path
  3. Singapore21108727120019982922356132337Shown above
  4. Amsterdam211087271200199829223561295632590This 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

98%

Seen by 63 of 64 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
RIPE NCC — Europe, Middle East, Central Asia
Country
United Kingdom
Allocated
7th February 2023
Allocation block
2a13:9500::/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 2a13:9500:1bf::/48
ROA prefixAuthorised originMax length
2a13:9500:1bf::/48AS211087/48

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 2a13:9500:1bf::/48
PrefixAddressesOriginVisibility
2a13:9500:1be::/4865.5k × /64AS201176DUND MC2 B.V.63/64

History

  1. AS21108722nd September 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.