bgpreport

Network · data from 2026-11-12

AS264070 AS264070 - FARIA & SCHIMITH LTDA - ME

Registry name: AS264070 - FARIA & SCHIMITH LTDA - ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264070, 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.
143.202.180.0/24 Invalid: maxLength Nonecovered by 143.202.180.0/23 2 0%low visibility 2
143.202.181.0/24 Invalid: maxLength Nonecovered by 143.202.180.0/23 2 0%low visibility 2
143.202.182.0/24 Invalid: maxLength Nonecovered by 143.202.180.0/22 2 0%low visibility 2
143.202.183.0/24 Invalid: maxLength Nonecovered by 143.202.180.0/22 2 0%low visibility 2
143.202.180.0/22 Valid Other IRR onlyRADB, TC 665 99% 67
2804:2a58::/32 Valid Other IRR onlyRADB, TC 630 99% 69
2804:2a58::/33 Valid Other IRR onlyTC 630 99% 69
2804:2a58:8000::/33 Valid Other IRR onlyTC 630 99% 69

AS-SET

AS264070 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 13 are in fix.csv.

  • ROA: maxLength4
  • Route object: none4
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength143.202.180.0/24ROA 143.202.180.0/22 AS264070 has maxLength 22; ROA 143.202.180.0/23 AS264070 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 143.202.180.0/24.2 of 673
Route object: none143.202.180.0/24No route object for it. A route object for 143.202.180.0/23 with origin AS264070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264070 in the RIR database for the space.2 of 673
ROA: maxLength143.202.181.0/24ROA 143.202.180.0/22 AS264070 has maxLength 22; ROA 143.202.180.0/23 AS264070 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 143.202.181.0/24.2 of 673
Route object: none143.202.181.0/24No route object for it. A route object for 143.202.180.0/23 with origin AS264070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264070 in the RIR database for the space.2 of 673
ROA: maxLength143.202.182.0/24ROA 143.202.180.0/22 AS264070 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 143.202.182.0/24.2 of 673
Route object: none143.202.182.0/24No route object for it. A route object for 143.202.180.0/22 with origin AS264070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264070 in the RIR database for the space.2 of 673
ROA: maxLength143.202.183.0/24ROA 143.202.180.0/22 AS264070 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 143.202.183.0/24.2 of 673
Route object: none143.202.183.0/24No route object for it. A route object for 143.202.180.0/22 with origin AS264070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264070 in the RIR database for the space.2 of 673
Route object: RIR143.202.180.0/22Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:2a58::/32Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:2a58::/33Route object only in TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:2a58:8000::/33Route object only in TC. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

143.202.180.0/23RADB, TCValid

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.