bgpreport

Network · data from 2026-11-12

AS50083 Hermes Telecom

Registry name: HERMES-TELECOM-BACKBONE Hermes Telecom BVBA, BE · PeeringDB

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

Announced routes

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

86.39.14.0/24 No ROA Nonecovered by 86.39.0.0/18 673 100% 66
192.139.62.0/24 No ROA Other origin only 673 100% 67
86.39.10.0/24 No ROA Nonecovered by 86.39.0.0/18 672 100% 67
2a05:9b80::/32 No ROA Nonecovered by 2a05:9b80::/29 635 100% 67
2a05:9b82:100::/40 No ROA Nonecovered by 2a05:9b80::/29 635 100% 67
2a05:9b82:200::/40 No ROA Nonecovered by 2a05:9b80::/29 635 100% 67
44.30.27.0/24 No ROA Other IRR onlyRADB 672 100% 67
86.39.0.0/18 No ROA RIR databaseRIPE 673 100% 67
91.208.164.0/24 No ROA RIR databaseRIPE 673 100% 67
185.83.136.0/22 No ROA RIR databaseRIPE 673 100% 67
2a00:1458::/32 No ROA RIR databaseRIPE 635 100% 67
2a05:9b80::/29 No ROA RIR databaseRIPE 634 100% 67
2a0a:44c0::/29 No ROA RIR databaseRIPE 634 100% 67
5.59.224.0/24 Valid Nonecovered by 5.59.224.0/22 672 100% 67
5.59.225.0/24 Valid Nonecovered by 5.59.224.0/22 672 100% 67
5.59.226.0/24 Valid Nonecovered by 5.59.224.0/22 672 100% 67
5.59.227.0/24 Valid Nonecovered by 5.59.224.0/22 672 100% 67
185.77.15.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS50083: AS-HERMESTELECOM. 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 (AS50083 isn't in the set, or no route object for AS50083 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 objectsAS50083 in itNot covered
AS-HERMESTELECOM RIPElists itself further down 3919356 Yes 1

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

  • ROA: none13
  • Route object: none10
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none86.39.14.0/24No ROA covers it. Add a ROA for AS50083, maxLength 24.673 of 673
Route object: none86.39.14.0/24No route object for it. A route object for 86.39.0.0/18 with origin AS50083 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50083 in the RIR database for the space.673 of 673
ROA: none192.139.62.0/24No ROA covers it. Add a ROA for AS50083, maxLength 24.673 of 673
Route object: none192.139.62.0/24Route objects for it name AS36236. Add a route object with origin AS50083 in the RIR database for the space.673 of 673
ROA: none86.39.10.0/24No ROA covers it. Add a ROA for AS50083, maxLength 24.672 of 673
Route object: none86.39.10.0/24No route object for it. A route object for 86.39.0.0/18 with origin AS50083 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50083 in the RIR database for the space.672 of 673
ROA: none2a05:9b80::/32No ROA covers it. Add a ROA for AS50083, maxLength 32.635 of 636
Route object: none2a05:9b80::/32No route object for it. A route object for 2a05:9b80::/29 with origin AS50083 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50083 in the RIR database for the space.635 of 636
ROA: none2a05:9b82:100::/40No ROA covers it. Add a ROA for AS50083, maxLength 40.635 of 636
Route object: none2a05:9b82:100::/40No route object for it. A route object for 2a05:9b80::/29 with origin AS50083 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50083 in the RIR database for the space.635 of 636
ROA: none2a05:9b82:200::/40No ROA covers it. Add a ROA for AS50083, maxLength 40.635 of 636
Route object: none2a05:9b82:200::/40No route object for it. A route object for 2a05:9b80::/29 with origin AS50083 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50083 in the RIR database for the space.635 of 636
ROA: none44.30.27.0/24No ROA covers it. Add a ROA for AS50083, maxLength 24.672 of 673
Route object: RIR44.30.27.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none86.39.0.0/18No ROA covers it. Add a ROA for AS50083, maxLength 18.673 of 673
ROA: none91.208.164.0/24No ROA covers it. Add a ROA for AS50083, maxLength 24.673 of 673
ROA: none185.83.136.0/22No ROA covers it. Add a ROA for AS50083, maxLength 22.673 of 673
ROA: none2a00:1458::/32No ROA covers it. Add a ROA for AS50083, maxLength 32.635 of 636
ROA: none2a05:9b80::/29No ROA covers it. Add a ROA for AS50083, maxLength 29.634 of 636
ROA: none2a0a:44c0::/29No ROA covers it. Add a ROA for AS50083, maxLength 29.634 of 636
Route object: none5.59.224.0/24No route object for it. A route object for 5.59.224.0/22 with origin AS50083 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50083 in the RIR database for the space.672 of 673
Route object: none5.59.225.0/24No route object for it. A route object for 5.59.224.0/22 with origin AS50083 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50083 in the RIR database for the space.672 of 673
Route object: none5.59.226.0/24No route object for it. A route object for 5.59.224.0/22 with origin AS50083 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50083 in the RIR database for the space.672 of 673
Route object: none5.59.227.0/24No route object for it. A route object for 5.59.224.0/22 with origin AS50083 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50083 in the RIR database for the space.672 of 673

Route objects not announced

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

5.59.224.0/22RIPEValid
185.202.224.0/22RIPENo ROA
185.233.218.0/24RIPENo ROA
188.209.144.0/20RADBNo ROA
2a0b:8780::/29RIPENo 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.