bgpreport

Network · data from 2026-11-12

AS213482 Waterfall

Registry name: WATERFALL Waterfall Technologies Ltd, GB · PeeringDB

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

Announced routes

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

2a12:bec6::/32 Invalid: origin None 47 7%low visibility 29
2a12:bec5::/32 Invalid: origin RIR databaseRIPE 5 1%low visibility 6
2a12:bec4:1780::/44 Valid None 635 100% 70
2a12:bec4:1c50::/44 Valid None 635 100% 70
2a12:bec4:1e40::/44 Valid None 635 100% 70
2a12:bec4:1e60::/44 Valid None 635 100% 70
2a12:bec4:1e70::/44 Valid None 635 100% 70
2a12:bec4:1e80::/44 Valid None 635 100% 70
2a12:bec4:1f40::/44 Valid None 635 100% 70
153.76.113.0/24 Valid RIR databaseRIPE 659 98% 66
82.23.170.0/24 Valid RIR databaseRADB, RIPE 658 98% 67
2a10:fa80:6000::/36 Valid RIR databaseRIPE 635 100% 70
2a12:bec4:2030::/44 Valid RIR databaseRIPE 635 100% 70
2a12:bec4:2040::/44 Valid RIR databaseRIPE 635 100% 70

AS-SET

PeeringDB's irr_as_set for AS213482: AS213482:AS-WATERFALL. 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 (AS213482 isn't in the set, or no route object for AS213482 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 objectsAS213482 in itNot covered
AS213482:AS-WATERFALL RIPE 4111 Yes 8

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

  • ROA: origin2
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: origin2a12:bec6::/32ROAs covering it name AS397423, not AS213482. If AS213482 should announce it, add a ROA for AS213482.47 of 636
Route object: none2a12:bec6::/32No route object for it. Add a route object with origin AS213482 in the RIR database for the space.47 of 636
ROA: origin2a12:bec5::/32ROAs covering it name AS397423, not AS213482. If AS213482 should announce it, add a ROA for AS213482.5 of 636
Route object: none2a12:bec4:1780::/44No route object for it. Add a route object with origin AS213482 in the RIR database for the space.635 of 636
Route object: none2a12:bec4:1c50::/44No route object for it. Add a route object with origin AS213482 in the RIR database for the space.635 of 636
Route object: none2a12:bec4:1e40::/44No route object for it. Add a route object with origin AS213482 in the RIR database for the space.635 of 636
Route object: none2a12:bec4:1e60::/44No route object for it. Add a route object with origin AS213482 in the RIR database for the space.635 of 636
Route object: none2a12:bec4:1e70::/44No route object for it. Add a route object with origin AS213482 in the RIR database for the space.635 of 636
Route object: none2a12:bec4:1e80::/44No route object for it. Add a route object with origin AS213482 in the RIR database for the space.635 of 636
Route object: none2a12:bec4:1f40::/44No route object for it. Add a route object with origin AS213482 in the RIR database for the space.635 of 636

Route objects not announced

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