bgpreport

Network · data from 2026-11-12

AS198178 INC-PARTNERS-365 365.partners INC

Registry name: INC-PARTNERS-365 365.partners INC, US · not in PeeringDB

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

Announced routes

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

2a13:7e40:3::/48 No ROA None 1 0%low visibility 1
185.164.172.0/24 No ROA RIR databaseRIPE 673 100% 67
195.93.253.0/24 No ROA RIR databaseRIPE 673 100% 67
2a0a:8d80:2::/48 No ROA RIR databaseRIPE 634 100% 67
109.61.110.0/24 Valid RIR databaseRIPE 673 100% 67
132.243.204.0/24 Valid RIR databaseRIPE 673 100% 67
146.19.102.0/24 Valid RIR databaseRIPE 673 100% 67
195.246.110.0/24 Valid RIR databaseRIPE 673 100% 67
77.91.127.0/24 Valid RIR databaseRIPE 672 100% 67
138.124.107.0/24 Valid RIR databaseRIPE 672 100% 67
212.102.107.0/24 Valid RIR databaseRIPE 672 100% 67
45.128.99.0/24 Valid RIR databaseRIPE 671 100% 68
83.242.100.0/24 Valid RIR databaseRIPE 671 100% 68
185.238.190.0/24 Valid RIR databaseRIPE 671 100% 67
138.124.111.0/24 Valid RIR databaseRIPE 670 100% 68
2a13:7e40:4::/48 Valid RIR databaseRIPE 635 100% 69
2a13:7e40:2::/48 Valid RIR databaseRIPE 632 99% 67

AS-SET

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

  • ROA: none4
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2a13:7e40:3::/48No ROA covers it. Add a ROA for AS198178, maxLength 48.1 of 636
Route object: none2a13:7e40:3::/48No route object for it. Add a route object with origin AS198178 in the RIR database for the space.1 of 636
ROA: none185.164.172.0/24No ROA covers it. Add a ROA for AS198178, maxLength 24.673 of 673
ROA: none195.93.253.0/24No ROA covers it. Add a ROA for AS198178, maxLength 24.673 of 673
ROA: none2a0a:8d80:2::/48No ROA covers it. Add a ROA for AS198178, maxLength 48.634 of 636

Route objects not announced

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

77.91.68.0/24RIPEInvalid: origin
138.124.81.0/24RIPEValid
2a13:7e40:1::/48RIPEValid
2a13:7e40:5::/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.