bgpreport

Network · data from 2026-11-12

AS395088 CONVERGIA-US - Convergia, inc

Registry name: CONVERGIA-US - Convergia, inc, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS395088, 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.
65.77.244.0/24 Valid Other IRR onlyNTTCOM 672 100% 67
65.77.245.0/24 Valid Other IRR onlyNTTCOM 672 100% 67
65.124.203.0/24 Valid Other IRR onlyNTTCOM 672 100% 67
199.77.202.0/24 Valid Other IRR onlyNTTCOM 672 100% 67
206.47.173.0/24 Valid Other IRR onlyNTTCOM 672 100% 67
206.47.178.0/24 Valid Other IRR onlyNTTCOM 672 100% 67
38.87.226.0/23 Valid RIR databaseARIN 672 100% 67
204.10.201.0/24 Valid RIR databaseARIN, NTTCOM 672 100% 67
204.10.202.0/24 Valid RIR databaseARIN, NTTCOM 672 100% 67
204.10.203.0/24 Valid RIR databaseARIN, NTTCOM 672 100% 67
204.10.204.0/24 Valid RIR databaseARIN, NTTCOM 672 100% 67
204.10.205.0/24 Valid RIR databaseARIN, NTTCOM 672 100% 67
204.10.206.0/24 Valid RIR databaseARIN, NTTCOM 672 100% 67
38.135.5.0/24 Valid RIR databaseARIN 671 100% 67

AS-SET

AS395088 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 6 are in fix.csv.

  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: RIR65.77.244.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR65.77.245.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR65.124.203.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR199.77.202.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR206.47.173.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR206.47.178.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS395088 is announced.

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.