bgpreport

Network · data from 2026-11-12

AS52053 REDHEBERG SAS

Registry name: REDHEBERG REDHEBERG Association declaree, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52053, 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.
155.117.152.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
170.39.216.0/24 Valid RIR databaseARIN 673 100% 67
170.39.218.0/24 Valid RIR databaseARIN 673 100% 67
185.255.112.0/24 Valid RIR databaseRIPE 673 100% 67
193.38.250.0/24 Valid RIR databaseRIPE 673 100% 67
2a13:9500:e7::/48 Valid RIR databaseRADB, RIPE 633 100% 67
2a14:1d00::/44 Valid RIR databaseRIPE 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS52053: RIPE::AS-REDHEBERG. 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 (AS52053 isn't in the set, or no route object for AS52053 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 objectsAS52053 in itNot covered
RIPE::AS-REDHEBERG In no IRR database read today.

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

  • AS-SET: not found1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
AS-SET: not foundRIPE::AS-REDHEBERGPeeringDB names RIPE::AS-REDHEBERG; no IRR database read has it.

Route objects not announced

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

2a10:4646:900::/44RIPEValid

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.