bgpreport

Network · data from 2026-11-12

AS49268 AMPR Belgium

Registry name: AMPR-BE Hermes Telecom BVBA, BE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS49268, 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.
44.11.0.0/16 No ROA Other IRR onlyALTDB, RADB 673 100% 67
2a01:9480::/32 No ROA RIR databaseALTDB, RADB, RIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS49268: AS-AMPR-BE. 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 (AS49268 isn't in the set, or no route object for AS49268 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 objectsAS49268 in itNot covered
AS-AMPR-BE RIPE 3144 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 3 are in fix.csv.

  • ROA: none2
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none44.11.0.0/16No ROA covers it. Add a ROA for AS49268, maxLength 16.673 of 673
Route object: RIR44.11.0.0/16Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
ROA: none2a01:9480::/32No ROA covers it. Add a ROA for AS49268, maxLength 32.635 of 636

Route objects not announced

Every route object with origin AS49268 is announced.

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.