subnet.im

82.153.48.0/20

GCI Network Solutions LimitedAS8851

At a glance

Addresses

4,096

/20 block

Visibility

100%

81 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCGB

Allocated 10th November 2003

AS paths to this prefix

All paths

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

OriginVantage point · Amsterdam
One AS path to 82.153.48.0/20 as seen from Amsterdam, read outward from the origin: AS8851 → AS25091 → AS8298. Each hop is listed with its network name beneath the graph.AS8851GCI Network Solut…OriginAS25091IP-Max SAAS8298IPng Networks GmbH

Seen from Amsterdam

  1. 1AS8851GCI Network Solutions LimitedGBOrigin
    Peer of AS8851seen on 439 paths from 3 vantage points
  2. 2AS25091IP-Max SACH
    Peer of AS25091seen on 666,530 paths from 2 vantage points
  3. 3AS8298IPng Networks GmbHCHVantage 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. Singapore8851132337This path
  2. Amsterdam8851250918298Shown above
  3. London, UK8851896635280This path
  4. Sao Paulo8851335635280This path
  5. Oregon, US8851693920130This 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

100%

Seen by 81 of 81 full-feed vantage points

Globally 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 Kingdom
Allocated
10th November 2003
Allocation block
82.152.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 82.153.48.0/20
ROA prefixAuthorised originMax length
82.152.0.0/15AS19905/24
82.152.0.0/15AS206509/15
82.152.0.0/15AS8851/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 82.153.48.0/20: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.82.152.0.0/15AS885182.153.48.0/20AS8851This prefix82.153.48.0/24AS17482.153.49.0/24AS19724682.153.50.0/24AS21073482.153.51.0/24AS5626482.153.52.0/24AS42689+7 more

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 82.153.48.0/20
PrefixAddressesOriginVisibility
82.152.0.0/15131kAS8851GCI Network Solutions Limited81/81

Sibling prefixes

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

History

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

Open 82.153.48.0/20 in the calculator/20 reference

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