bgpreport

Network · data from 2026-11-12

AS136900 IQ NET

Registry name: IQNETNSW-AS-AP - IQ NET (NSW) PTY LTD, AU · PeeringDB

10IPv4 routes 90.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No 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 AS136900, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136900, 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.
203.83.208.0/21 No ROA Other IRR onlyRADB 672 100% 67
103.60.20.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.151.78.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.190.18.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.190.19.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.126.12.0/22 Valid RIR databaseAPNIC 671 100% 67
103.126.12.0/24 Valid RIR databaseAPNIC 671 100% 67
103.126.13.0/24 Valid RIR databaseAPNIC 671 100% 67
103.126.14.0/24 Valid RIR databaseAPNIC 671 100% 67
103.126.15.0/24 Valid RIR databaseAPNIC 671 100% 67
2001:df4:c500::/48 Valid RIR databaseAPNIC, NTTCOM, RADB 636 100% 69
2400:8ba0::/32 Valid RIR databaseAPNIC, NTTCOM, RADB 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS136900: AS-SET. 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 (AS136900 isn't in the set, or no route object for AS136900 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 objectsAS136900 in itNot covered
AS-SET RADB 010 No 12
AFRINIC (also) 111 No 12
ARIN (also) 010 No 12
RIPE (also)1 member set in no database: AS200105:AS-HK 38151,451 No 12

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

  • ROA: none1
  • Route object: RIR1
  • AS-SET: own ASN1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none203.83.208.0/21No ROA covers it. Add a ROA for AS136900, maxLength 21.672 of 673
Route object: RIR203.83.208.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
AS-SET: own ASNAS-SETAS136900 isn't in AS-SET (RADB) once expanded. Add AS136900 to it.

Route objects not announced

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

103.190.18.0/23APNIC, RADBValid

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.