bgpreport

Network · data from 2026-11-12

AS262978 Armazém Datacenter

Registry name: AS262978 - Centro de Tecnologia Armazem Datacenter LTDA., BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262978, 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:4d44:14:8020::/64 Invalid: maxLength Nonecovered by 2804:4d44::/32 2 0%low visibility 3
2804:4d44:14:8021::/64 Invalid: maxLength Nonecovered by 2804:4d44::/32 2 0%low visibility 3
2804:4d44:14:8022::/64 Invalid: maxLength Nonecovered by 2804:4d44::/32 2 0%low visibility 3
2804:4d44:14:8023::/64 Invalid: maxLength Nonecovered by 2804:4d44::/32 2 0%low visibility 3
2804:4d44:ada:2150::/64 Invalid: maxLength Nonecovered by 2804:4d44:ada::/48 2 0%low visibility 3
2804:4d44:ada:8001::/64 Invalid: maxLength Nonecovered by 2804:4d44:ada::/48 2 0%low visibility 3
2804:4d44:ada:8002::/64 Invalid: maxLength Nonecovered by 2804:4d44:ada::/48 2 0%low visibility 3
132.255.220.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
132.255.220.0/24 Valid Other IRR onlyTC 672 100% 66
132.255.221.0/24 Valid Other IRR onlyTC 672 100% 66
132.255.222.0/24 Valid Other IRR onlyTC 672 100% 66
132.255.223.0/24 Valid Other IRR onlyTC 672 100% 66
143.0.120.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
143.0.122.0/24 Valid Other IRR onlyTC 672 100% 66
143.0.123.0/24 Valid Other IRR onlyTC 672 100% 66
186.250.184.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
186.250.184.0/24 Valid Other IRR onlyTC 672 100% 66
186.250.185.0/24 Valid Other IRR onlyTC 672 100% 66
186.250.187.0/24 Valid Other IRR onlyTC 672 100% 66
143.0.120.0/24 Valid Other IRR onlyTC 671 100% 66
143.0.121.0/24 Valid Other IRR onlyTC 671 100% 66
186.250.186.0/24 Valid Other IRR onlyTC 671 100% 66
2804:4d44::/32 Valid Other IRR onlyRADB, TC 635 100% 69
2804:4d44:c::/48 Valid Other IRR onlyTC 635 100% 69
2804:4d44:10::/48 Valid Other IRR onlyTC 635 100% 69
2804:4d44:ada::/48 Valid Other IRR onlyRADB, TC 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS262978: AS262978:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS262978 isn't in the set, or no route object for AS262978 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS262978 in itNot covered
AS262978:AS-CUSTOMERS TC 3123 No 26

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

  • ROA: maxLength7
  • Route object: none7
  • Route object: RIR19
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:4d44:14:8020::/64ROA 2804:4d44::/32 AS262978 has maxLength 32; the route is a /64. Raise the maxLength, or add a ROA for 2804:4d44:14:8020::/64.2 of 636
Route object: none2804:4d44:14:8020::/64No route object for it. A route object for 2804:4d44::/32 with origin AS262978 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS262978 in the RIR database for the space.2 of 636
ROA: maxLength2804:4d44:14:8021::/64ROA 2804:4d44::/32 AS262978 has maxLength 32; the route is a /64. Raise the maxLength, or add a ROA for 2804:4d44:14:8021::/64.2 of 636
Route object: none2804:4d44:14:8021::/64No route object for it. A route object for 2804:4d44::/32 with origin AS262978 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS262978 in the RIR database for the space.2 of 636
ROA: maxLength2804:4d44:14:8022::/64ROA 2804:4d44::/32 AS262978 has maxLength 32; the route is a /64. Raise the maxLength, or add a ROA for 2804:4d44:14:8022::/64.2 of 636
Route object: none2804:4d44:14:8022::/64No route object for it. A route object for 2804:4d44::/32 with origin AS262978 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS262978 in the RIR database for the space.2 of 636
ROA: maxLength2804:4d44:14:8023::/64ROA 2804:4d44::/32 AS262978 has maxLength 32; the route is a /64. Raise the maxLength, or add a ROA for 2804:4d44:14:8023::/64.2 of 636
Route object: none2804:4d44:14:8023::/64No route object for it. A route object for 2804:4d44::/32 with origin AS262978 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS262978 in the RIR database for the space.2 of 636
ROA: maxLength2804:4d44:ada:2150::/64ROA 2804:4d44::/32 AS262978 has maxLength 32; ROA 2804:4d44:ada::/48 AS262978 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2804:4d44:ada:2150::/64.2 of 636
Route object: none2804:4d44:ada:2150::/64No route object for it. A route object for 2804:4d44:ada::/48 with origin AS262978 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS262978 in the RIR database for the space.2 of 636
ROA: maxLength2804:4d44:ada:8001::/64ROA 2804:4d44::/32 AS262978 has maxLength 32; ROA 2804:4d44:ada::/48 AS262978 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2804:4d44:ada:8001::/64.2 of 636
Route object: none2804:4d44:ada:8001::/64No route object for it. A route object for 2804:4d44:ada::/48 with origin AS262978 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS262978 in the RIR database for the space.2 of 636
ROA: maxLength2804:4d44:ada:8002::/64ROA 2804:4d44::/32 AS262978 has maxLength 32; ROA 2804:4d44:ada::/48 AS262978 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2804:4d44:ada:8002::/64.2 of 636
Route object: none2804:4d44:ada:8002::/64No route object for it. A route object for 2804:4d44:ada::/48 with origin AS262978 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS262978 in the RIR database for the space.2 of 636
Route object: RIR132.255.220.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR132.255.220.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR132.255.221.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR132.255.222.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR132.255.223.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR143.0.120.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR143.0.122.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR143.0.123.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.250.184.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.250.184.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.250.185.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.250.187.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR143.0.120.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR143.0.121.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR186.250.186.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:4d44::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:4d44:c::/48Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:4d44:10::/48Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:4d44:ada::/48Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
AS-SET: own ASNAS262978:AS-CUSTOMERSAS262978 isn't in AS262978:AS-CUSTOMERS (TC) once expanded. Add AS262978 to it.

Route objects not announced

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