bgpreport

Network · data from 2026-11-12

AS7005 Internet Services SA -7005

Registry name: AS7005 - InterServer SA, AR · PeeringDB

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

Announced routes

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

200.0.212.0/24 No ROA Other IRR onlyRADB 669 99% 67
200.0.208.0/24 No ROA Other IRR onlyRADB 3 0%low visibility 3

AS-SET

AS7005'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 10 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none200.0.212.0/24No ROA covers it. Add a ROA for AS7005, maxLength 24.669 of 673
Route object: RIR200.0.212.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none200.0.208.0/24No ROA covers it. Add a ROA for AS7005, maxLength 24.3 of 673
Route object: RIR200.0.208.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

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

200.0.211.0/24RADBNo ROA
200.0.213.0/24RADBNo ROA
200.0.214.0/24RADBNo ROA
200.0.215.0/24RADBNo ROA
200.115.24.0/24LACNICValid
200.115.28.0/22LACNICValid

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.