bgpreport

Network · data from 2026-11-12

AS149248 Hightech Broadband Services

Registry name: HIGHTECH1-AS-IN - Hightech Broadband Services Pvt Ltd, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149248, 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.

103.179.20.0/24 Valid RIR databaseAPNIC 673 100% 66
103.179.20.0/23 Valid RIR databaseAPNIC 671 100% 66
103.179.21.0/24 Valid RIR databaseAPNIC 671 100% 66
2400:4a60::/32 Valid RIR databaseAPNIC 636 100% 70
2400:4a60::/35 Valid RIR databaseAPNIC 636 100% 70
2400:4a60:2000::/35 Valid RIR databaseAPNIC 636 100% 70
2400:4a60:4000::/35 Valid RIR databaseAPNIC 636 100% 70
2400:4a60:6000::/35 Valid RIR databaseAPNIC 636 100% 70
2400:4a60:8000::/35 Valid RIR databaseAPNIC 636 100% 70
2400:4a60:a000::/35 Valid RIR databaseAPNIC 636 100% 70
2400:4a60:c000::/35 Valid RIR databaseAPNIC 636 100% 70
2400:4a60:e000::/35 Valid RIR databaseAPNIC 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS149248: APNIC::AS149248:AS-HIGHTECH1-IN. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS149248 isn't in the set, or no route object for AS149248 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS149248 in itNot covered
APNIC::AS149248:AS-HIGHTECH1-IN APNIC 2155 Yes 0

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 6 are in fix.csv.

  • Route object: not announced6

Route objects not announced

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

2400:4a60::/33APNICValid
2400:4a60::/34APNICValid
2400:4a60:4000::/34APNICValid
2400:4a60:8000::/33APNICValid
2400:4a60:8000::/34APNICValid
2400:4a60:c000::/34APNICValid

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.