bgpreport

Network · data from 2026-11-12

AS211575 RuiNetwork

Registry name: RuiNetwork Rui Feng, CN · PeeringDB

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

Announced routes

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

199.19.22.0/24 Valid RIR databaseARIN 672 100% 66
2a0f:85c1:bfe::/48 Valid RIR databaseRIPE 636 100% 69
2a14:67c1:b514::/48 Valid RIR databaseRIPE 635 100% 69
2a14:67c1:b563::/48 Valid RIR databaseRIPE 635 100% 69
2a14:67c1:b578::/48 Valid RIR databaseRIPE 635 100% 69
2a14:67c1:b588::/48 Valid RIR databaseRIPE 635 100% 69
2a14:67c1:b5e0::/44 Valid RIR databaseRIPE 635 100% 69
2a0f:1cc5:4600::/40 Valid RIR databaseRADB, RIPE 634 100% 70
2a0f:1cc5:4650::/44 Valid RIR databaseRIPE 634 100% 68
2a0f:1cc6:b250::/44 Valid RIR databaseRIPE 634 100% 69
2a14:67c1:b586::/48 Valid RIR databaseRIPE 634 100% 68
2a14:67c1:b589::/48 Valid RIR databaseRIPE 634 100% 67
2a14:67c1:b590::/48 Valid RIR databaseRIPE 634 100% 67
2a14:7583:f4f4::/48 Valid RIR databaseRIPE 634 100% 67
2a14:67c1:b500::/40 Valid RIR databaseRADB, RIPE 633 100% 70
2a14:7583:f411::/48 Valid RIR databaseRIPE 633 100% 67
102.216.82.0/24 Valid RIR databaseAFRINIC, RADB 615 91% 67
2a14:67c1:b587::/48 Valid RIR databaseRIPE 605 95% 68
2a0f:1cc5:4620::/44 Valid RIR databaseRIPE 574 90% 67
2a14:67c1:b533::/48 Valid RIR databaseRIPE 554 87% 67
2a0f:1cc5:4640::/44 Valid RIR databaseRIPE 484 76% 66
2a0f:1cc5:4610::/44 Valid RIR databaseRIPE 338 53% 64
2a0f:1cc5:4630::/44 Valid RIR databaseRIPE 94 15% 43
2a14:67c1:b511::/48 Valid RIR databaseRIPE 9 1%low visibility 7
2a14:67c1:b531::/48 Valid RIR databaseRIPE 4 1%low visibility 5
2a14:7583:f4f0::/48 Valid RIR databaseRIPE 3 0%low visibility 4
2a0f:1cc5:fff::/48 Valid RIR databaseRIPE 1 0%low visibility 3
2a14:67c1:b530::/44 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS211575: AS211575:AS-RUINETWORK. 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 (AS211575 isn't in the set, or no route object for AS211575 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 objectsAS211575 in itNot covered
AS211575:AS-RUINETWORK RIPE 32156 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 54 are in fix.csv.

  • Route object: not announced54

Route objects not announced

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

2406:840:e260::/44APNICValid
2406:840:e260::/45APNICValid
2406:840:e260::/46APNICValid
2406:840:e260::/47APNICValid
2406:840:e260::/48APNICValid
2406:840:e261::/48APNICValid
2406:840:e262::/47APNICValid
2406:840:e262::/48APNICValid
2406:840:e263::/48APNICValid
2406:840:e264::/46APNICValid
2406:840:e264::/47APNICValid
2406:840:e264::/48APNICValid
2406:840:e265::/48APNICValid
2406:840:e266::/47APNICValid
2406:840:e266::/48APNICValid
2406:840:e267::/48APNICValid
2406:840:e268::/45APNICValid
2406:840:e268::/46APNICValid
2406:840:e268::/47APNICValid
2406:840:e268::/48APNICValid
2406:840:e269::/48APNICValid
2406:840:e26a::/47APNICValid
2406:840:e26a::/48APNICValid
2406:840:e26b::/48APNICValid
2406:840:e26c::/46APNICValid
2406:840:e26c::/47APNICValid
2406:840:e26c::/48APNICValid
2406:840:e26d::/48APNICValid
2406:840:e26e::/47APNICValid
2406:840:e26e::/48APNICValid
2406:840:e26f::/48APNICValid
2602:f92a:a478::/48ARINValid
2602:f9f6:480::/44ARINValid
2a0f:1cc5:ffff::/48RIPENo ROA
2a0f:9400:6110::/48RIPEValid
2a12:cb47:ffff::/48RIPEValid
2a13:9500:a0::/48RIPEValid
2a14:67c1:b500::/48RIPEValid
2a14:67c1:b501::/48RIPEValid
2a14:67c1:b549::/48RIPEValid
2a14:67c1:b561::/48RIPEValid
2a14:67c1:b566::/48RIPEValid
2a14:67c1:b581::/48RIPEValid
2a14:67c1:b582::/48RIPEValid
2a14:67c1:b591::/48RIPEValid
2a14:67c1:b599::/48RIPEValid
2a14:67c1:b5a1::/48RIPEValid
2a14:7583:f460::/44RIPEValid
2a14:7583:f46a::/48RIPEValid
2a14:7583:f46c::/48RIPEValid
2a14:7583:f46e::/48RIPEValid
2a14:7583:f4fc::/48RIPEValid
2a14:7583:f4fe::/48RIPEValid
2a14:7dc0:506::/48RIPEValid

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.