bgpreport

Network · data from 2026-11-12

AS134915 GIGABYTESBROADBAND-AS - Gigabytes Broadband Pvt Ltd

Registry name: GIGABYTESBROADBAND-AS - Gigabytes Broadband Pvt Ltd, IN · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS134915, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134915, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

31.77.115.0/24 Invalid: origin Other origin only 2 0%low visibility 2

AS-SET

AS134915 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 12 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: origin31.77.115.0/24ROAs covering it name AS198661, not AS134915. If AS134915 should announce it, add a ROA for AS134915.2 of 673
Route object: none31.77.115.0/24Route objects for it name AS198661. Add a route object with origin AS134915 in the RIR database for the space.2 of 673

Route objects not announced

Route objects with origin AS134915 whose prefix no peer sees AS134915 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.114.156.0/22APNICNo ROA
45.114.156.0/24RADBNo ROA
45.114.157.0/24RADBNo ROA
45.114.158.0/24RADBNo ROA
45.114.159.0/24RADBNo ROA
103.54.96.0/22APNICNo ROA
103.54.96.0/24RADBNo ROA
103.54.97.0/24RADBNo ROA
103.54.98.0/24RADBNo ROA
103.54.99.0/24RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.