bgpreport

Network · data from 2026-11-12

AS151712 Multireach Broadband Services Private Limited

Registry name: MULTIREACHBROADBANDSERVICES-AS-IN - Multireach Broadband Services Private Limited, IN · PeeringDB

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

Announced routes

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

43.248.58.0/23 No ROA Other origin only 671 100% 67
103.86.95.0/24 No ROA RIR databaseAPNIC 669 99% 67
103.44.157.0/24 Valid RIR databaseAPNIC 672 100% 66
103.252.241.0/24 Valid RIR databaseAPNIC 672 100% 66
45.114.36.0/24 Valid RIR databaseAPNIC 671 100% 66
45.114.38.0/24 Valid RIR databaseAPNIC 671 100% 66
103.44.156.0/24 Valid RIR databaseAPNIC 671 100% 67
103.44.158.0/24 Valid RIR databaseAPNIC 671 100% 67
103.44.159.0/24 Valid RIR databaseAPNIC 671 100% 66
45.114.37.0/24 Valid RIR databaseAPNIC 670 100% 67
45.114.39.0/24 Valid RIR databaseAPNIC 670 100% 67
2001:df3:1ac0::/48 Valid RIR databaseAPNIC 636 100% 69
43.248.58.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29
43.248.59.0/24 Valid RIR databaseAPNIC 43 6%low visibility 29

AS-SET

PeeringDB's irr_as_set for AS151712: AS151712:AS-MULTIREACHBROADBANDSERVICES. 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 (AS151712 isn't in the set, or no route object for AS151712 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 objectsAS151712 in itNot covered
AS151712:AS-MULTIREACHBROADBANDSERVICES APNIC 5259 Yes 1

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

  • ROA: none2
  • Route object: none1
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none43.248.58.0/23No ROA covers it. Add a ROA for AS151712, maxLength 23.671 of 673
Route object: none43.248.58.0/23Route objects for it name AS38197, AS55725. Add a route object with origin AS151712 in the RIR database for the space.671 of 673
ROA: none103.86.95.0/24No ROA covers it. Add a ROA for AS151712, maxLength 24.669 of 673

Route objects not announced

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

103.44.156.0/22APNICValid
103.44.156.0/23APNICValid
103.44.158.0/23APNICValid
103.194.156.0/22APNICNo ROA
103.194.156.0/23APNICNo ROA
103.194.156.0/24APNICNo ROA
103.194.157.0/24APNICNo ROA
103.194.158.0/23APNICNo ROA
103.194.158.0/24APNICNo ROA
103.194.159.0/24APNICNo ROA
2001:df0:3380::/48APNICNo 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.