bgpreport

Network · data from 2026-11-12

AS196954 epcan

Registry name: epcan Epcan GmbH, DE · PeeringDB

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

Announced routes

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

185.190.52.0/22 Invalid: origin None 2 0%low visibility 2
149.50.176.0/20 Valid Other IRR onlyRADB 671 100% 68
85.190.248.0/22 Valid RIR databaseRIPE 671 100% 68
85.208.238.0/24 Valid RIR databaseRIPE 671 100% 68
85.208.239.0/24 Valid RIR databaseRIPE 671 100% 68
91.194.132.0/23 Valid RIR databaseRIPE 671 100% 68
91.239.92.0/23 Valid RIR databaseRIPE 671 100% 68
130.255.120.0/21 Valid RIR databaseRIPE 671 100% 68
145.63.192.0/20 Valid RIR databaseRIPE 671 100% 68
149.107.128.0/20 Valid RIR databaseARIN 671 100% 68
185.28.116.0/24 Valid RIR databaseRIPE 671 100% 68
185.63.124.0/22 Valid RIR databaseRIPE 671 100% 68
185.118.124.0/24 Valid RIR databaseRIPE 671 100% 68
2a04:9740::/29 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS196954: RIPE::AS-EPCAN. 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 (AS196954 isn't in the set, or no route object for AS196954 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 objectsAS196954 in itNot covered
RIPE::AS-EPCAN RIPE 3118 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 3 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: origin185.190.52.0/22ROAs covering it name AS218764, not AS196954. If AS196954 should announce it, add a ROA for AS196954.2 of 673
Route object: none185.190.52.0/22No route object for it. Add a route object with origin AS196954 in the RIR database for the space.2 of 673
Route object: RIR149.50.176.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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