bgpreport

Network · data from 2026-11-12

AS135671 RBB InfoTech

Registry name: RBB-AS-AP - RBB InfoTech, CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135671, 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.
44.31.28.0/24 No ROA Other IRR onlyALTDB 668 99% 67
2a0e:aa06:440::/48 No ROA RIR databaseRIPE 634 100% 69
2a0e:aa06:450::/44 Valid RIR databaseRIPE 635 100% 69
2a14:67c2:520::/48 Valid RIR databaseRIPE 634 100% 69

AS-SET

AS135671's PeeringDB record names no 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 7 are in fix.csv.

  • ROA: none2
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none44.31.28.0/24No ROA covers it. Add a ROA for AS135671, maxLength 24.668 of 673
Route object: RIR44.31.28.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none2a0e:aa06:440::/48No ROA covers it. Add a ROA for AS135671, maxLength 48.634 of 636

Route objects not announced

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

2401:8c40::/32RADBNo ROA
2a14:67c2:500::/40RADB, RIPEValid
2a14:67c2:519::/48RIPEValid
2a14:67c3:caf0::/44RIPENo 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.