bgpreport

Network · data from 2026-11-12

AS204613 OverdriveHost

Registry name: OverdriveHost Emrick Jean Michel Barraud, FR · PeeringDB

0IPv4 routes
2IPv6 routes 50.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No 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 AS204613, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS204613, 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.
2a05:dfc1:9000::/40 No ROA RIR databaseRIPE 635 100% 67
2a10:4646:260::/44 Valid RIR databaseRIPE 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS204613: AS204613:AS-OVERDRIVEHOST. 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 (AS204613 isn't in the set, or no route object for AS204613 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 objectsAS204613 in itNot covered
AS204613:AS-OVERDRIVEHOST RIPE 010 No 2

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.

  • ROA: none1
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: none2a05:dfc1:9000::/40No ROA covers it. Add a ROA for AS204613, maxLength 40.635 of 636
AS-SET: own ASNAS204613:AS-OVERDRIVEHOSTAS204613 isn't in AS204613:AS-OVERDRIVEHOST (RIPE) once expanded. Add AS204613 to it.

Route objects not announced

Every route object with origin AS204613 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.