bgpreport

Network · data from 2026-11-12

AS200430 WEBO

Registry name: airee WEBO LLC, RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200430, 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.107.72.0/24 Invalid: origin Other origin only 2 0%low visibility 2
185.107.73.0/24 Invalid: origin Other origin only 2 0%low visibility 2
185.107.72.0/22 No ROA Other origin only 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS200430: RIPE::AS200430. 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 (AS200430 isn't in the set, or no route object for AS200430 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 objectsAS200430 in itNot covered
RIPE::AS200430 A single AS number, not a set: AS200430 (this network), 3 route objects.

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: origin2
  • ROA: none1
  • Route object: none3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin185.107.72.0/24ROAs covering it name AS207353, not AS200430. If AS200430 should announce it, add a ROA for AS200430.2 of 673
Route object: none185.107.72.0/24Route objects for it name AS207353. Add a route object with origin AS200430 in the RIR database for the space.2 of 673
ROA: origin185.107.73.0/24ROAs covering it name AS207353, not AS200430. If AS200430 should announce it, add a ROA for AS200430.2 of 673
Route object: none185.107.73.0/24Route objects for it name AS207353. Add a route object with origin AS200430 in the RIR database for the space.2 of 673
ROA: none185.107.72.0/22No ROA covers it. Add a ROA for AS200430, maxLength 22.2 of 673
Route object: none185.107.72.0/22Route objects for it name AS27257. Add a route object with origin AS200430 in the RIR database for the space.2 of 673

Route objects not announced

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

2a06:4480::/29RIPENo ROA
2a06:4480:beef::/48RIPENo ROA
2a06:4480:c0de::/48RIPENo 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.