bgpreport

Network · data from 2026-11-12

AS153168 LUBIN-AS-AP - Lu Bin

Registry name: LUBIN-AS-AP - Lu Bin, CN · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 0.0% with a route object
6IPv6 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
2Low visibility seen by under 10% of full-table peers
27Route objects not announced registered with origin AS153168, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS153168, 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.
79.183.2.0/24 Invalid: origin None 1 0%low visibility 1
2406:840:fd50::/48 Valid RIR databaseAPNIC 636 100% 68
2406:840:fd56::/48 Valid RIR databaseAPNIC 635 100% 67
2406:840:fd59::/48 Valid RIR databaseAPNIC 635 100% 67
2406:840:fe9a::/48 Valid RIR databaseAPNIC 635 100% 69
2406:840:fd55::/48 Valid RIR databaseAPNIC 634 100% 67
2406:840:fd58::/48 Valid RIR databaseAPNIC 1 0%low visibility 1

AS-SET

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

  • ROA: origin1
  • Route object: none1
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
ROA: origin79.183.2.0/24ROAs covering it name AS834, not AS153168. If AS153168 should announce it, add a ROA for AS153168.1 of 673
Route object: none79.183.2.0/24No route object for it. Add a route object with origin AS153168 in the RIR database for the space.1 of 673

Route objects not announced

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

216.236.50.0/24RIPEValid
2406:840:fd50::/44APNICValid
2406:840:fd50::/45APNICValid
2406:840:fd50::/46APNICValid
2406:840:fd50::/47APNICValid
2406:840:fd51::/48APNICValid
2406:840:fd52::/47APNICValid
2406:840:fd52::/48APNICValid
2406:840:fd53::/48APNICValid
2406:840:fd54::/46APNICValid
2406:840:fd54::/47APNICValid
2406:840:fd54::/48APNICValid
2406:840:fd56::/47APNICValid
2406:840:fd57::/48APNICValid
2406:840:fd58::/45APNICValid
2406:840:fd58::/46APNICValid
2406:840:fd58::/47APNICValid
2406:840:fd5a::/47APNICValid
2406:840:fd5a::/48APNICValid
2406:840:fd5b::/48APNICValid
2406:840:fd5c::/46APNICValid
2406:840:fd5c::/47APNICValid
2406:840:fd5c::/48APNICValid
2406:840:fd5d::/48APNICValid
2406:840:fd5e::/47APNICValid
2406:840:fd5e::/48APNICValid
2406:840:fd5f::/48APNICValid

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.