subnet.im

2.27.196.0/22

Ace Data Centers II, L.L.C.AS401152

GTT Communications Inc.AS3257

Announced by more than one origin AS (MOAS).

At a glance

Addresses

1,024

/22 block

Visibility

82%

62 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 21st September 2010

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 2.27.196.0/22 as seen from Sao Paulo, read outward from the origin: AS401152 → AS11798 → AS174 → AS6453 → AS35280. Each hop is listed with its network name beneath the graph.AS401152Ace Data Centers …OriginAS11798Ace Data Centers,…AS174Cogent Communicat…AS6453TATA Communicatio…AS35280F5 Networks SARL

Seen from Sao Paulo

  1. 1AS401152Ace Data Centers II, L.L.C.USOrigin
    Peer of AS401152seen on 20,605 paths from 138 vantage points
  2. 2AS11798Ace Data Centers, Inc.US
    Peer of AS11798seen on 8,304 paths from 61 vantage points
  3. 3AS174Cogent Communications, LLCUS
    Peer of AS174seen on 638,691 paths from 47 vantage points
  4. 4AS6453TATA Communications (America) IncUS
    Peer of AS6453seen on 652,531 paths from 6 vantage points
  5. 5AS35280F5 Networks SARLFRVantage 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. Singapore32572376423673This path
  2. Oregon, US3257855142013This path
  3. London, UK4011521179864618529This path
  4. Amsterdam401152117986461250918298This path
  5. Sao Paulo40115211798174645335280Shown 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. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

82%

Seen by 62 of 76 full-feed vantage points

Partially propagated

Observed at 5 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 States
Allocated
21st September 2010
Allocation block
2.26.0.0/15
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 2.27.196.0/22
ROA prefixAuthorised originMax length
2.27.196.0/22AS401152/24

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 2.27.196.0/22
PrefixAddressesOriginVisibility
2.27.192.0/221kAS17404Pipe Networks LLC1/76

History

  1. AS325712th August 2026 — present
  2. AS4011524th October 2026 — present
  3. AS40040212th August 2026 — 6th 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.

Open 2.27.196.0/22 in the calculator/22 reference

Routing data derived from RouteViews MRT archives and public registry data.