bgpreport

Network · data from 2026-11-12

AS215760 DisPaisy Enterprises

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

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

Announced routes

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

2001:67c:5c0::/48 No ROA None 3 0%low visibility 3
2a06:a002::/32 No ROA RIR databaseRIPE 3 0%low visibility 3
2a0b:4e07:c00::/38 No ROA RIR databaseRIPE 3 0%low visibility 3
2a14:7583:e100::/40 No ROA RIR databaseRIPE 3 0%low visibility 4
2a06:a002:140::/44 Valid RIR databaseRIPE 636 100% 67
2a06:a002:153::/48 Valid RIR databaseRIPE 636 100% 69
2a06:a002:c70::/44 Valid RIR databaseRIPE 636 100% 69
2a06:a002:f000::/44 Valid RIR databaseRIPE 636 100% 69
2a0b:4e07:c02::/48 Valid RIR databaseRIPE 636 100% 69
2a0f:6284:30::/44 Valid RIR databaseRIPE 636 100% 69
2a06:a002:a010::/44 Valid RIR databaseRIPE 635 100% 69
2a06:a002:aca5::/48 Valid RIR databaseRIPE 635 100% 69
2a14:7583:e1b0::/44 Valid RIR databaseRIPE 635 100% 69
2a06:a002:a100::/40 Valid RIR databaseRIPE 634 100% 67
2a06:a002:f00d::/48 Valid RIR databaseRIPE 634 100% 69
2a0b:4e07:c99::/48 Valid RIR databaseRIPE 634 100% 69
2a14:7583:e1ac::/48 Valid RIR databaseRIPE 3 0%low visibility 4

AS-SET

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

  • ROA: none4
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2001:67c:5c0::/48No ROA covers it. Add a ROA for AS215760, maxLength 48.3 of 636
Route object: none2001:67c:5c0::/48No route object for it. Add a route object with origin AS215760 in the RIR database for the space.3 of 636
ROA: none2a06:a002::/32No ROA covers it. Add a ROA for AS215760, maxLength 32.3 of 636
ROA: none2a0b:4e07:c00::/38No ROA covers it. Add a ROA for AS215760, maxLength 38.3 of 636
ROA: none2a14:7583:e100::/40No ROA covers it. Add a ROA for AS215760, maxLength 40.3 of 636

Route objects not announced

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

2a02:2fc0:2a::/48RIPEValid
2a0b:4e07:20::/46RIPEValid
2a12:bec4:1fa0::/44RIPEValid
2a14:67c2:f00::/40RIPEValid

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.