bgpreport

Network · data from 2026-11-12

AS209630 KREDIT-AS LLC VASH KREDIT BANK

Registry name: KREDIT-AS LLC VASH KREDIT BANK, UA · not in PeeringDB

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

Announced routes

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

194.77.38.0/24 Invalid: origin Other origin only 1 0%low visibility 1
185.218.138.0/24 No ROA None 0 0%low visibility 1
93.123.118.0/24 Valid Other IRR onlyRADB 672 100% 66
31.57.208.0/24 Valid RIR databaseRIPE 673 100% 66
151.241.144.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
181.214.125.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
181.215.41.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
181.215.186.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
151.243.11.0/24 Valid RIR databaseRADB, RIPE 671 100% 66

AS-SET

AS209630 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: origin1
  • ROA: none1
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: origin194.77.38.0/24ROAs covering it name AS834, not AS209630. If AS209630 should announce it, add a ROA for AS209630.1 of 673
Route object: none194.77.38.0/24Route objects for it name AS834. Add a route object with origin AS209630 in the RIR database for the space.1 of 673
ROA: none185.218.138.0/24No ROA covers it. Add a ROA for AS209630, maxLength 24.0 of 673
Route object: none185.218.138.0/24No route object for it. Add a route object with origin AS209630 in the RIR database for the space.0 of 673
Route object: RIR93.123.118.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

85.11.167.0/24RIPEValid
91.92.40.0/24RIPEValid
91.92.41.0/24RIPEValid
91.92.42.0/24RIPEValid
93.152.233.0/24RIPEValid
94.125.102.0/24RIPEValid
217.60.180.0/24RIPEValid

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.