bgpreport

Network · data from 2026-11-12

AS148992 TOIINDIA

Registry name: TOIINDIA - THINGS OF INDIA (OPC) PRIVATE LIMITED, IN · PeeringDB

11IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
1Route objects not announced registered with origin AS148992, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS148992, 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.6.90.0/23 Valid RIR databaseAPNIC 672 100% 66
103.61.195.0/24 Valid RIR databaseAPNIC 672 100% 66
103.66.20.0/22 Valid RIR databaseAPNIC 672 100% 66
103.162.178.0/24 Valid RIR databaseAPNIC 672 100% 66
103.170.46.0/23 Valid RIR databaseAPNIC 672 100% 66
103.178.192.0/23 Valid RIR databaseAPNIC 672 100% 66
103.216.200.0/24 Valid RIR databaseAPNIC 672 100% 66
163.61.228.0/23 Valid RIR databaseAPNIC 672 100% 66
163.61.228.0/24 Valid RIR databaseAPNIC 672 100% 66
163.61.229.0/24 Valid RIR databaseAPNIC 672 100% 66
163.223.192.0/23 Valid RIR databaseAPNIC 672 100% 66
2401:f2a0::/32 Valid RIR databaseAPNIC 636 100% 70

AS-SET

PeeringDB's irr_as_set for AS148992: AS148992:AS-PEERS. 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 (AS148992 isn't in the set, or no route object for AS148992 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 objectsAS148992 in itNot covered
AS148992:AS-PEERS APNIClists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE 7147420,801 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.

  • AS-SET: missing member5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS148992:AS-PEERSAS148992:AS-PEERS (APNIC) lists AS-6186; no IRR database read has it.
AS-SET: missing memberAS148992:AS-PEERSAS148992:AS-PEERS (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it.
AS-SET: missing memberAS148992:AS-PEERSAS148992:AS-PEERS (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it.
AS-SET: missing memberAS148992:AS-PEERSAS148992:AS-PEERS (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it.
AS-SET: missing memberAS148992:AS-PEERSAS148992:AS-PEERS (APNIC) lists AS214174:AS-RIPE; no IRR database read has it.

Route objects not announced

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

103.170.65.0/24APNICValid

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.