subnet.im

77.107.95.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCGB

Allocated 18th December 2006

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 77.107.95.0/24 as seen from London, UK, read outward from the origin: AS154950 → AS55470 → AS55836 → AS64049 → AS8529. Each hop is listed with its network name beneath the graph.AS154950CRAPPLET INFOTECH…OriginAS55470Cyfuture India Pv…AS55836Reliance Jio Info…AS64049Reliance Jio Info…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS154950seen on 148 paths from 66 vantage points
  2. Peer of AS55470seen on 6,159 paths from 102 vantage points
  3. Peer of AS55836seen on 518,155 paths from 138 vantage points
  4. Peer of AS64049seen on 4,298 paths from 2 vantage points

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. Amsterdam1549505547055836640498298This path
  2. London, UK1549505547055836640498529Shown above
  3. Sao Paulo15495055470558366404935280This path
  4. Singapore15495055470558366404923673This path
  5. Oregon, US154950554705583664049855142013This 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 76 of 76 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
18th December 2006
Allocation block
77.107.64.0/18
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 77.107.95.0/24
ROA prefixAuthorised originMax length
77.107.95.0/24AS154950/24
77.107.95.0/24AS20473/24
77.107.95.0/24AS212306/24
77.107.64.0/18AS19905/24
77.107.64.0/18AS8851/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 77.107.95.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.77.107.64.0/18AS885177.107.95.0/24AS154950This prefix77.107.94.0/24AS3257

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 77.107.95.0/24
PrefixAddressesOriginVisibility
77.107.64.0/1816.4kAS8851GCI Network Solutions Limited76/76

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 77.107.95.0/24
PrefixAddressesOriginVisibility
77.107.94.0/24256AS3257GTT Communications Inc.76/76

History

  1. AS15495012th October 2026 — present
  2. AS21230612th August 2026 — 12th October 2026
  3. AS1549505th October 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 77.107.95.0/24 in the calculator/24 reference

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