bgpreport

Network · data from 2026-11-12

AS24753 Globecomm Europe

Registry name: GCE-NET Globecomm Europe B.V., NL · PeeringDB

14IPv4 routes 71.4% RPKI valid · 71.4% with a route object
0IPv6 routes
4RPKI invalid 0 origin · 4 maxLength
0No ROA 4 with no route object for this origin
7Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS24753, seen from no peer

Announced routes

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

62.32.32.252/32 Invalid: maxLength Nonecovered by 62.32.32.0/24 0 0%low visibility 1
62.32.32.253/32 Invalid: maxLength Nonecovered by 62.32.32.0/24 0 0%low visibility 1
62.32.32.254/32 Invalid: maxLength Nonecovered by 62.32.32.0/24 0 0%low visibility 1
62.32.32.255/32 Invalid: maxLength Nonecovered by 62.32.32.0/24 0 0%low visibility 1
62.32.32.0/24 Valid RIR databaseRIPE 673 100% 66
89.21.172.0/24 Valid RIR databaseRIPE 673 100% 66
89.21.173.0/24 Valid RIR databaseRIPE 673 100% 66
89.21.181.0/24 Valid RIR databaseRIPE 673 100% 66
213.187.132.0/22 Valid RIR databaseRIPE 673 100% 66
213.187.139.0/24 Valid RIR databaseRIPE 673 100% 66
213.187.152.0/22 Valid RIR databaseRIPE 673 100% 66
81.85.52.0/22 Valid RIR databaseRIPE 2 0%low visibility 2
81.85.96.0/22 Valid RIR databaseRIPE 2 0%low visibility 2
81.85.100.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS24753: AS24753:AS-CUSTOMERS. 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 (AS24753 isn't in the set, or no route object for AS24753 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 objectsAS24753 in itNot covered
AS24753:AS-CUSTOMERS RIPE 181338 Yes 4

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

  • ROA: maxLength4
  • Route object: none4
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: maxLength62.32.32.252/32ROA 62.32.32.0/24 AS24753 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 62.32.32.252/32.0 of 673
Route object: none62.32.32.252/32No route object for it. A route object for 62.32.32.0/24 with origin AS24753 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24753 in the RIR database for the space.0 of 673
ROA: maxLength62.32.32.253/32ROA 62.32.32.0/24 AS24753 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 62.32.32.253/32.0 of 673
Route object: none62.32.32.253/32No route object for it. A route object for 62.32.32.0/24 with origin AS24753 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24753 in the RIR database for the space.0 of 673
ROA: maxLength62.32.32.254/32ROA 62.32.32.0/24 AS24753 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 62.32.32.254/32.0 of 673
Route object: none62.32.32.254/32No route object for it. A route object for 62.32.32.0/24 with origin AS24753 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24753 in the RIR database for the space.0 of 673
ROA: maxLength62.32.32.255/32ROA 62.32.32.0/24 AS24753 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 62.32.32.255/32.0 of 673
Route object: none62.32.32.255/32No route object for it. A route object for 62.32.32.0/24 with origin AS24753 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24753 in the RIR database for the space.0 of 673

Route objects not announced

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

64.49.156.0/23RIPE-NONAUTHNo ROA
81.85.160.0/20RIPEValid
81.85.160.0/22RIPEInvalid: maxLength
202.174.71.0/24RIPE-NONAUTHNo ROA
202.174.72.0/22RIPE-NONAUTHNo ROA
208.84.18.0/24RIPE-NONAUTHNo ROA
213.187.128.0/19RADBNo ROA
2a00:df8::/32RIPEValid

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.