bgpreport

Network · data from 2026-11-12

AS50311 Gloman

Registry name: GLOMAN Gloman SA, GR · PeeringDB

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

Announced routes

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

154.57.18.0/24 No ROA Other IRR onlyRADB 671 100% 68
83.174.158.0/24 No ROA RIR databaseRIPE 673 100% 67
154.43.72.0/24 No ROA RIR databaseARIN 671 100% 68
193.162.7.0/24 No ROA RIR databaseRIPE 671 100% 68
193.104.200.0/24 No ROA RIR databaseRIPE 670 100% 68
2a10:5040::/29 No ROA RIR databaseRIPE 632 99% 67
91.220.131.0/24 Valid RIR databaseRIPE 671 100% 68
2a04:3e00:1000::/48 Valid RIR databaseRIPE 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS50311: AS50311. 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 (AS50311 isn't in the set, or no route object for AS50311 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 objectsAS50311 in itNot covered
AS50311 A single AS number, not a set: AS50311 (this network), 10 route objects.

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

  • ROA: none6
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none154.57.18.0/24No ROA covers it. Add a ROA for AS50311, maxLength 24.671 of 673
Route object: RIR154.57.18.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none83.174.158.0/24No ROA covers it. Add a ROA for AS50311, maxLength 24.673 of 673
ROA: none154.43.72.0/24No ROA covers it. Add a ROA for AS50311, maxLength 24.671 of 673
ROA: none193.162.7.0/24No ROA covers it. Add a ROA for AS50311, maxLength 24.671 of 673
ROA: none193.104.200.0/24No ROA covers it. Add a ROA for AS50311, maxLength 24.670 of 673
ROA: none2a10:5040::/29No ROA covers it. Add a ROA for AS50311, maxLength 29.632 of 636

Route objects not announced

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

185.254.216.0/24RIPENo ROA
2001:470:585::/48ARINValid

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.