bgpreport

Network · data from 2026-11-12

AS52177 Glecom

Registry name: GLECOM Resona Glecom AB, SE · PeeringDB

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

Announced routes

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

2a12:5800::/33 Invalid: maxLength Nonecovered by 2a12:5800::/32 1 0%low visibility 1
2a12:5800::/34 Invalid: maxLength Nonecovered by 2a12:5800::/32 1 0%low visibility 1
192.121.29.0/24 Valid RIR databaseRIPE 669 99% 67
194.26.208.0/24 Valid RIR databaseRIPE 669 99% 67
2a12:5800::/29 Valid RIR databaseRIPE 634 100% 69
2a12:5800::/32 Valid RIR databaseRIPE 634 100% 69
2a12:5800::/30 Valid RIR databaseRIPE 633 100% 69
2a12:5800::/31 Valid RIR databaseRIPE 633 100% 69

AS-SET

PeeringDB's irr_as_set for AS52177: AS-GLECOM. 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 (AS52177 isn't in the set, or no route object for AS52177 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 objectsAS52177 in itNot covered
AS-GLECOM RIPE 219 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.

  • ROA: maxLength2
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength2a12:5800::/33ROA 2a12:5800::/29 AS52177 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2a12:5800::/33.1 of 636
Route object: none2a12:5800::/33No route object for it. A route object for 2a12:5800::/32 with origin AS52177 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52177 in the RIR database for the space.1 of 636
ROA: maxLength2a12:5800::/34ROA 2a12:5800::/29 AS52177 has maxLength 32; the route is a /34. Raise the maxLength, or add a ROA for 2a12:5800::/34.1 of 636
Route object: none2a12:5800::/34No route object for it. A route object for 2a12:5800::/32 with origin AS52177 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52177 in the RIR database for the space.1 of 636

Route objects not announced

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

2a0e:b107:b90::/44RIPENo ROA
2a10:2f00:136::/48RIPENo 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.