bgpreport

Network · data from 2026-11-12

AS270837 L N DE CAMPOS

Registry name: AS270837 - Imartech Fibra, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270837, 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.
2804:722c:4000::/34 Valid Nonecovered by 2804:722c::/32 635 100% 67
2804:722c::/34 Valid Nonecovered by 2804:722c::/32 629 99% 67
2804:722c:8000::/34 Valid Nonecovered by 2804:722c::/32 629 99% 67
177.52.140.0/22 Valid Other IRR onlyRADB, TC 664 99% 66
177.52.140.0/24 Valid Other IRR onlyRADB, TC 663 99% 67
177.52.141.0/24 Valid Other IRR onlyRADB, TC 663 99% 67
177.52.142.0/24 Valid Other IRR onlyRADB, TC 663 99% 67
177.52.143.0/24 Valid Other IRR onlyRADB, TC 662 98% 67
2804:722c::/32 Valid Other IRR onlyRADB, TC 630 99% 69

AS-SET

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

  • Route object: none3
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: none2804:722c:4000::/34No route object for it. A route object for 2804:722c::/32 with origin AS270837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270837 in the RIR database for the space.635 of 636
Route object: none2804:722c::/34No route object for it. A route object for 2804:722c::/32 with origin AS270837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270837 in the RIR database for the space.629 of 636
Route object: none2804:722c:8000::/34No route object for it. A route object for 2804:722c::/32 with origin AS270837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270837 in the RIR database for the space.629 of 636
Route object: RIR177.52.140.0/22Route object only in RADB, TC. Add it in the RIR database for the space.664 of 673
Route object: RIR177.52.140.0/24Route object only in RADB, TC. Add it in the RIR database for the space.663 of 673
Route object: RIR177.52.141.0/24Route object only in RADB, TC. Add it in the RIR database for the space.663 of 673
Route object: RIR177.52.142.0/24Route object only in RADB, TC. Add it in the RIR database for the space.663 of 673
Route object: RIR177.52.143.0/24Route object only in RADB, TC. Add it in the RIR database for the space.662 of 673
Route object: RIR2804:722c::/32Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636

Route objects not announced

Every route object with origin AS270837 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.