bgpreport

Network · data from 2026-11-12

AS267212 WEB 8 DATA CENTER LTDA

Registry name: AS267212 - WEB 8 DATA CENTER LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267212, 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.
204.157.124.0/24 No ROA RIR databaseARIN 670 100% 67
45.231.132.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
45.231.132.0/24 Valid Other IRR onlyTC 671 100% 67
45.231.133.0/24 Valid Other IRR onlyTC 670 100% 67
45.231.134.0/24 Valid Other IRR onlyTC 670 100% 67
45.231.135.0/24 Valid Other IRR onlyTC 670 100% 67
2804:49fc::/32 Valid Other IRR onlyRADB, TC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS267212: AS-SM. 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 (AS267212 isn't in the set, or no route object for AS267212 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 objectsAS267212 in itNot covered
AS-SM RADB 1114 No 7

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

  • ROA: none1
  • Route object: RIR6
  • AS-SET: own ASN1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none204.157.124.0/24No ROA covers it. Add a ROA for AS267212, maxLength 24.670 of 673
Route object: RIR45.231.132.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.231.132.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.231.133.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.231.134.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.231.135.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:49fc::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
AS-SET: own ASNAS-SMAS267212 isn't in AS-SM (RADB) once expanded. Add AS267212 to it.

Route objects not announced

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

45.231.132.0/23TCValid
45.231.134.0/23TCValid
2804:49fc::/33TCValid
2804:49fc:8000::/33TCValid

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.