bgpreport

Network · data from 2026-11-12

AS45204 Gemnet

Registry name: GEMNET-MN - GEMNET LLC, MN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45204, 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.157.184.229/32 Invalid: origin None 0 0%low visibility 1
103.9.88.144/29 Invalid: maxLength Nonecovered by 103.9.88.0/22 0 0%low visibility 1
103.9.90.100/32 Invalid: maxLength Nonecovered by 103.9.88.0/22 0 0%low visibility 1
103.9.90.128/26 Invalid: maxLength Nonecovered by 103.9.88.0/22 0 0%low visibility 1
103.9.90.131/32 Invalid: maxLength Nonecovered by 103.9.88.0/22 0 0%low visibility 1
103.9.91.115/32 Invalid: maxLength Nonecovered by 103.9.88.0/22 0 0%low visibility 1
180.149.95.0/24 Valid RIR databaseAPNIC 672 100% 67
180.149.97.0/24 Valid RIR databaseAPNIC 672 100% 67
180.149.103.0/24 Valid RIR databaseAPNIC 672 100% 67
180.149.64.0/20 Valid RIR databaseAPNIC 671 100% 67
180.149.80.0/21 Valid RIR databaseAPNIC 671 100% 67
180.149.90.0/24 Valid RIR databaseAPNIC 671 100% 67
180.149.91.0/24 Valid RIR databaseAPNIC 671 100% 67
180.149.93.0/24 Valid RIR databaseAPNIC 671 100% 67
180.149.94.0/24 Valid RIR databaseAPNIC 671 100% 67
180.149.96.0/24 Valid RIR databaseAPNIC 671 100% 67
180.149.98.0/24 Valid RIR databaseAPNIC 671 100% 67
180.149.99.0/24 Valid RIR databaseAPNIC 671 100% 67
180.149.100.0/22 Valid RIR databaseAPNIC 671 100% 67
180.149.104.0/21 Valid RIR databaseAPNIC 671 100% 67
180.149.112.0/20 Valid RIR databaseAPNIC 671 100% 67
2401:d600::/32 Valid RIR databaseAPNIC, RADB 635 100% 67
203.26.189.158/32 Valid RIR databaseAPNIC 24 4%low visibility 20

AS-SET

PeeringDB's irr_as_set for AS45204: AS-GEMNET. 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 (AS45204 isn't in the set, or no route object for AS45204 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 objectsAS45204 in itNot covered
AS-GEMNET RADB 6311,631 Yes 6
APNIC (also) 73261,168 Yes 6
RIPE (also) 216 No 23

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

  • ROA: origin1
  • ROA: maxLength5
  • Route object: none6
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: origin103.157.184.229/32ROAs covering it name AS55342, not AS45204. If AS45204 should announce it, add a ROA for AS45204.0 of 673
Route object: none103.157.184.229/32No route object for it. Add a route object with origin AS45204 in the RIR database for the space.0 of 673
ROA: maxLength103.9.88.144/29ROA 103.9.88.0/22 AS45204 has maxLength 22; the route is a /29. Raise the maxLength, or add a ROA for 103.9.88.144/29.0 of 673
Route object: none103.9.88.144/29No route object for it. A route object for 103.9.88.0/22 with origin AS45204 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45204 in the RIR database for the space.0 of 673
ROA: maxLength103.9.90.100/32ROA 103.9.88.0/22 AS45204 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 103.9.90.100/32.0 of 673
Route object: none103.9.90.100/32No route object for it. A route object for 103.9.88.0/22 with origin AS45204 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45204 in the RIR database for the space.0 of 673
ROA: maxLength103.9.90.128/26ROA 103.9.88.0/22 AS45204 has maxLength 22; the route is a /26. Raise the maxLength, or add a ROA for 103.9.90.128/26.0 of 673
Route object: none103.9.90.128/26No route object for it. A route object for 103.9.88.0/22 with origin AS45204 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45204 in the RIR database for the space.0 of 673
ROA: maxLength103.9.90.131/32ROA 103.9.88.0/22 AS45204 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 103.9.90.131/32.0 of 673
Route object: none103.9.90.131/32No route object for it. A route object for 103.9.88.0/22 with origin AS45204 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45204 in the RIR database for the space.0 of 673
ROA: maxLength103.9.91.115/32ROA 103.9.88.0/22 AS45204 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 103.9.91.115/32.0 of 673
Route object: none103.9.91.115/32No route object for it. A route object for 103.9.88.0/22 with origin AS45204 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45204 in the RIR database for the space.0 of 673

Route objects not announced

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

103.9.88.0/22APNICValid
180.149.64.0/18APNIC, RADBValid
180.149.64.0/19APNICValid
180.149.64.0/21APNICValid
180.149.72.0/21APNICValid
180.149.80.0/20APNICValid
180.149.88.0/21APNICValid
180.149.92.0/24APNICInvalid: maxLength
180.149.96.0/19APNICValid
180.149.96.0/20APNICValid
180.149.96.0/21APNICValid
180.149.100.0/23APNICValid
180.149.100.0/24APNICValid
180.149.101.0/24APNICValid
180.149.102.0/23APNICValid
180.149.102.0/24APNICValid
180.149.112.0/21APNICValid
180.149.112.0/24APNICValid
180.149.117.0/24APNICValid
180.149.118.0/24APNICValid
180.149.120.0/21APNICValid

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.