bgpreport

Network · data from 2026-11-12

AS204085 DisPaisy's Projects

Registry name: DISPAISY-AS2 Adam Grazioli, IT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS204085, 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.
2a06:a002:b352::/48 No ROA None 2 0%low visibility 2
2a06:9801:3::/48 Valid RIR databaseRIPE 635 100% 69
2a06:a002:a002::/48 Valid RIR databaseRIPE 635 100% 69
2a06:a002:c450::/44 Valid RIR databaseRIPE 635 100% 69
2a14:67c3:1b0::/44 Valid RIR databaseRIPE 635 100% 69
2a14:7583:e111::/48 Valid RIR databaseRIPE 635 100% 69
2a06:a002:4085::/48 Valid RIR databaseRIPE 634 100% 69
2a06:a002:d323::/48 Valid RIR databaseRADB, RIPE 634 100% 67
2a14:67c3:1b2::/48 Valid RIR databaseRIPE 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS204085: RIPE::AS204085:AS-ALL. 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 (AS204085 isn't in the set, or no route object for AS204085 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 objectsAS204085 in itNot covered
RIPE::AS204085:AS-ALL RIPE 1110 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 4 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a06:a002:b352::/48No ROA covers it. Add a ROA for AS204085, maxLength 48.2 of 636
Route object: none2a06:a002:b352::/48No route object for it. Add a route object with origin AS204085 in the RIR database for the space.2 of 636

Route objects not announced

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

2a12:bec4:1fa0::/44RIPEValid
2a14:67c3:1b3::/48RIPEValid

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.