bgpreport

Network · data from 2026-11-12

AS133648 MNR Broadband Services

Registry name: MAGNUS-TELELINKS-AS - MNR Broadband Services Pvt. Ltd., IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133648, 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.231.56.0/22 Valid RIR databaseAPNIC 672 100% 67
43.243.38.0/24 Valid RIR databaseAPNIC 672 100% 67
43.243.39.0/24 Valid RIR databaseAPNIC 672 100% 67
103.44.18.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.50.148.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.50.150.0/23 Valid RIR databaseAPNIC 672 100% 67
103.79.168.0/22 Valid RIR databaseAPNIC 672 100% 67
103.79.248.0/22 Valid RIR databaseAPNIC 672 100% 67
103.95.164.0/22 Valid RIR databaseAPNIC 672 100% 67
103.163.62.0/23 Valid RIR databaseAPNIC 672 100% 67
103.167.98.0/23 Valid RIR databaseAPNIC 672 100% 67
103.170.152.0/23 Valid RIR databaseAPNIC 672 100% 67
103.170.152.0/24 Valid RIR databaseAPNIC 672 100% 67
103.170.153.0/24 Valid RIR databaseAPNIC 672 100% 67
45.248.3.0/24 Valid RIR databaseAPNIC 671 100% 67
43.231.58.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
43.231.56.0/24 Valid RIR databaseAPNIC, RADB 6 1%low visibility 4
43.231.57.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4
43.231.59.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4
103.50.150.0/24 Valid RIR databaseAPNIC, RADB 6 1%low visibility 4
103.79.168.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4
103.79.169.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4
103.79.170.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4
103.79.248.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4
103.79.249.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4
103.79.250.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4
103.79.251.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4
103.95.164.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4
103.95.165.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4
103.95.167.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4
43.231.56.0/23 Valid RIR databaseAPNIC 5 1%low visibility 3
43.231.58.0/23 Valid RIR databaseAPNIC 5 1%low visibility 3
103.79.168.0/23 Valid RIR databaseAPNIC 5 1%low visibility 3
103.79.248.0/23 Valid RIR databaseAPNIC 5 1%low visibility 3
103.79.250.0/23 Valid RIR databaseAPNIC 5 1%low visibility 3
103.95.164.0/23 Valid RIR databaseAPNIC 5 1%low visibility 3
103.95.166.0/23 Valid RIR databaseAPNIC 5 1%low visibility 3
103.163.62.0/24 Valid RIR databaseAPNIC 5 1%low visibility 3
103.163.63.0/24 Valid RIR databaseAPNIC 5 1%low visibility 3
103.167.98.0/24 Valid RIR databaseAPNIC 5 1%low visibility 3
103.167.99.0/24 Valid RIR databaseAPNIC 5 1%low visibility 3
103.79.170.0/23 Valid RIR databaseAPNIC 3 0%low visibility 2
103.79.171.0/24 Valid RIR databaseAPNIC 3 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS133648: AS133648:AS-CUSTOMERS. 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 (AS133648 isn't in the set, or no route object for AS133648 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 objectsAS133648 in itNot covered
AS133648:AS-CUSTOMERS RADBlists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE 7277820,907 Yes 0
APNIC (also)lists itself further down6 member sets in no database: AS-6186, AS134026:AS-CUSTOMERS, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE … 4965612,520 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 12 are in fix.csv.

  • AS-SET: missing member5
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS133648:AS-CUSTOMERSAS133648:AS-CUSTOMERS (RADB) lists AS-6186; no IRR database read has it.
AS-SET: missing memberAS133648:AS-CUSTOMERSAS133648:AS-CUSTOMERS (RADB) lists AS-HNSISP-TRANSIT; no IRR database read has it.
AS-SET: missing memberAS133648:AS-CUSTOMERSAS133648:AS-CUSTOMERS (RADB) lists AS136346:AS-FASTTNET; no IRR database read has it.
AS-SET: missing memberAS133648:AS-CUSTOMERSAS133648:AS-CUSTOMERS (RADB) lists AS137609:AS-DCSISPL; no IRR database read has it.
AS-SET: missing memberAS133648:AS-CUSTOMERSAS133648:AS-CUSTOMERS (RADB) lists AS214174:AS-RIPE; no IRR database read has it.

Route objects not announced

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

103.50.151.0/24APNICValid
103.61.254.0/23APNICInvalid: origin
103.92.115.0/24APNICValid
103.95.166.0/24APNICValid
103.119.196.0/22APNICInvalid: origin
103.119.196.0/24APNICInvalid: origin
2403:8dc0::/32APNICNo 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.