bgpreport

Network · data from 2026-11-12

AS207168 Business Trade

Registry name: BUSINESS-TRADE-AS Business Trade Ltd, RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207168, 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.
85.142.180.0/32 Invalid: maxLength Nonecovered by 85.142.180.0/22 2 0%low visibility 1
178.236.139.1/32 Invalid: maxLength Nonecovered by 178.236.139.0/24 2 0%low visibility 1
212.192.47.0/24 No ROA RIR databaseRIPE 671 100% 68
77.91.98.0/23 Valid RIR databaseRIPE 673 100% 66
77.91.125.0/24 Valid RIR databaseRIPE 673 100% 66
85.142.180.0/22 Valid RIR databaseRIPE 673 100% 66
178.236.139.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS207168'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 11 are in fix.csv.

  • ROA: maxLength2
  • ROA: none1
  • Route object: none2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: maxLength85.142.180.0/32ROA 85.142.180.0/22 AS207168 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 85.142.180.0/32.2 of 673
Route object: none85.142.180.0/32No route object for it. A route object for 85.142.180.0/22 with origin AS207168 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207168 in the RIR database for the space.2 of 673
ROA: maxLength178.236.139.1/32ROA 178.236.139.0/24 AS207168 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 178.236.139.1/32.2 of 673
Route object: none178.236.139.1/32No route object for it. A route object for 178.236.139.0/24 with origin AS207168 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207168 in the RIR database for the space.2 of 673
ROA: none212.192.47.0/24No ROA covers it. Add a ROA for AS207168, maxLength 24.671 of 673

Route objects not announced

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

77.91.98.0/24RIPEInvalid: maxLength
77.91.99.0/24RIPEInvalid: maxLength
2a00:1e68:98::/47RIPEInvalid: origin
2a00:1e68:98::/48RIPEInvalid: origin
2a00:1e68:99::/48RIPEInvalid: origin
2a00:1e68:125::/48RIPEInvalid: origin

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.