bgpreport

Network · data from 2026-11-12

AS30889 Waycom International

Registry name: WAYCOM-AS ADISTA SAS, FR · PeeringDB

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

Announced routes

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

207.241.200.0/22 Invalid: origin RIR databaseARIN 64 10%low visibility 39
193.27.195.0/24 Valid RIR databaseRIPE 530 79% 66

AS-SET

PeeringDB's irr_as_set for AS30889: AS-WAYCOM. 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 (AS30889 isn't in the set, or no route object for AS30889 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 objectsAS30889 in itNot covered
AS-WAYCOM RIPE 91679 Yes 0

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

  • ROA: origin1
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: origin207.241.200.0/22ROAs covering it name AS16347, not AS30889. If AS30889 should announce it, add a ROA for AS30889.64 of 673

Route objects not announced

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

45.145.124.0/22RIPEValid
79.98.96.0/21RIPEValid
185.15.128.0/22RIPEValid
185.95.120.0/22RIPEValid
185.105.28.0/22RIPENo ROA
185.149.8.0/22RIPEValid
185.151.52.0/22RIPENo ROA
185.172.16.0/22RIPEValid
185.196.248.0/22RIPEValid
193.27.194.0/24RIPEValid
193.201.146.0/25RIPENo ROA
194.177.32.0/19RIPEValid
195.214.240.0/21RIPEValid
2a01:6d8::/32RIPEValid
2a03:1e60::/32RIPENo ROA
2a03:bf40::/32RIPEInvalid: origin
2a07:7740::/29RIPENo ROA

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.